Key concepts

We provide complementary client and server SDKs to complete your integration:

  • The client SDKs enable you to securely collect payment information from your customers
  • The server SDKs enable you to act on the collected payment information

We have SDKs for the following client platforms and server languages:

Client SDKs Server SDKs
  • Android
  • iOS
  • JavaScript
  • Java
  • .Net
  • Node.js
  • PHP
  • Python
  • Ruby

The client SDKs require authorization. In this guide, we'll use a client token – the most flexible form of authorization.

Both the client and server SDKs use payment method nonces to refer to payment information. In this guide, we'll use a payment method nonce to create a transaction.

note

For information about the basics of processing and how you can use our features to best fit your business, see our support articles.

How it works

Client and server payment token flow Diagram demonstrating the required interaction between the client, our servers, and your server.
  1. Your app or web front-end requests a client token from your server in order to initialize the client SDK
  2. Your server generates and sends a client token back to your client with the server SDK
  3. Once the client SDK is initialized and the customer has submitted payment information, the SDK communicates that information and returns a payment method nonce
  4. You then send the payment method nonce to your server
  5. Your server code receives the payment method nonce from your client and then uses the server SDK to create a transaction or perform other functions detailed in the guides
note

See our example integrations for a working demonstration.

API keys

Get your sandbox or production API keys from the Control Panel to complete your integration. Once you're ready to go live, be sure to switch from your sandbox API keys to production.

Next: Set Up Your Client →

Still have questions?

If you can’t find an answer, contact our Support team.