So, you’ve been told you need to use to process payments. There are many decisions to make to get started, but the biggest is perhaps deciding how your system will interact with

This post, which is the latest in MIL’s series, will address selecting the interface that’s best for you. MIL was the first organization to integrate Salesforce with and we hope that our experience will help to guide you through a successful transition.

Let’s get started. has three interfaces:

  1. A payment form managed by
  2. A web service integration where captures the payment information
  3. A web service integration where your system captures the payment information Payment Form

The simplest integration is having create a payment form for your needs. You can choose the data fields you want to capture along with the payment types you want to allow. Payment forms presently in use can be found here.

The first page of the payment form process contains details about the person making the payment and, typically, their account number. The next page captures information about the payment itself, such as the payor’s bank account or credit card details. A confirmation page can then be shown to the user, offering a payment button for processing.

The big advantage of this approach is that you don’t need to do much. creates and manages the payment form pages for you. One downside, however, is your system doesn’t know anything about payments until after the fact. You find out about payments that have been made when you download the previous day’s transactions from For each transaction, you can match up the account number for the payment with the account number in your system. However, if the user entered the account number incorrectly in the payment form, you’ll need to have a plan to deal with those cases.

Web Service Integration with Capturing Payment Details

A deeper level of integration can be achieved by having your system call through a SOAP web service, with capturing the payment information, and then redirecting back to your system.

The steps to follow for this integration are:

  1. Create a Payment ID. This will typically be an auto-incremented field because it must be unique to each payment
  2. Decide on redirect URLs for to use after payment authorization. One URL is used if the payment is successfully authorized and a different URL is used if it is not
  3. Call through a SOAP web service to get their unique identifier for the payment (known as a token). When calling the web service, you’ll need to pass in the Payment ID from your system, the amount to be charged, the ID of the account at to use (known as the TCS App ID), and the success and failure URLs. will return the token
  4. Redirect from your system to, passing in the token and the TCS App ID as parameters will then display a page where the user can select the type of payment and enter in the payment details. will redirect back into your system using one of the two URLs you provided in step two, above. If the payment authorization failed or the user cancelled out of it, your page should allow the user to attempt payment again. If the payment authorization was successful, your page will need to make another SOAP web service call back to to confirm the payment. Once this returns a successful response, you can update your system that the payment was made.

When integrating with through this approach, the payment process is friendlier to the user than using the payment form. The user doesn’t have to enter an account number and details of the fields can be prepopulated when you redirect to After payment authorization the user is also redirected back into your system, providing a much more seamless process.

Web Service Integration with Your System Capturing Payment Details

A final option for integration is to avoid showing any user interface. Your system can ask the user for the payment details and then make a SOAP web service call to to process the payment.

The advantage to this approach is that your system can maintain a user interface that is consistent between your normal system pages and payment pages. However, the downside is that your system is storing payment information, whether temporary or permanent. Ultimately, this can lead to additional work when your system is audited for government standards. It can also increase user apprehension about using your system, as they’ll need to provide their payment details to another entity.

Summary has three interfaces that allow the processing of payments. Depending on factors of time and effort for the integration, your comfort level of storing payment information from users, and the need to provide a consistent user interface, you can make the best integration decision for your needs.

Cary Freeman is a developer with 17 years of Java development and two years of Salesforce development. He holds 12 certifications, including a Salesforce Certified Application Architect, Salesforce Certified System Architect, and Project Management Professional (PMP).