Triple Play Pay API

For developers who prefer their native language or who don’t have a development app that converts calls to REST, we offer robust Software Development Kits.

See Available SDKs Here

Using REST

Triple Play Pay API endpoints return secure JSON metadata that you can utilize for a personalized payment experience.

Sandbox & Development Certificate

For smooth integration and stakeholder satisfaction, Triple Play Pay has built a quick certification process that utilizes a test API Key in our Sandbox environment to ensure that developers have the resources and know-how to properly utilize our endpoints, requests, and responses for successful transactions and user experiences.

Go to the certification page >

API Utilities

Our payment processing API provides endpoints for common payment workflows like authorizing charges, settling authorized amounts, and tokenizing payment methods for future use. It also provides endpoints for more advanced functionality such as retrieving transaction history, uploading signatures and documents required for merchant onboarding, and more. Below are some key notes for use of the API endpoints.

Generating a Failed Charge

When processing charges, it's important to note that any transaction made with the Sandbox URL for $3.33 will fail. This is so that you can see the reponse for a failed transaction.

Duplicate Charge Catching

The API also has duplicate charge prevention enabled by default. If you submit multiple charges for the same amount on the same card or bank account within a single day, the second and subsequent charges will fail. If you need to process many similar charges in a short timeframe, you can request duplicate protection to be disabled for your account.

Authorizations for Future Charges

For authorizing a charge without completing it right away, use the "authorize" endpoint. This will check for available funds on the provided payment method. Once authorized, you can submit the "settle" or "charge" requests with the authorized amount to complete the transaction.

Saving Payment Details for Future Charges

To generate a tokenized version of a payment method like a card or bank account, use the "card" or "bankaccount" endpoint. The returned token can be safely stored and used for future "charge" requests.

Endpoints