Stored Payment Tokens

Overview

The Stored Payment Tokens (Cards-on-File) API helps you to store and manage payment tokens on your e/m-commerce sites easily. Integration with our platform is simple with easy to use interfaces.

Authentication-Making the first API request is only few steps away

All projects start in Sandbox mode. Once you’re invited to gain access to this API you can login here to get Client Application ID (API Key), Client Application Secret, Consumer Application Secret and API Plan name.
All API requests must be authenticated with an OAuth token. To get the OAuth token, follow these simple steps.
1. Make a HTTP POST request to the endpoint /auth/oauth/v2/token with HTTP Authorization Header as Basic base64encoded(client_application_id:client_application_secret), Content-Type as application/x-www-form-urlencoded and Cache-Control as no-cache.
2. The response would contain an OAuth token along with token type and token expiry in seconds.
Once an OAuth token is obtained, you can use the token along with Consumer Application Secret and API Plan name provided during Sandbox access in the HTTP Header of an API to make your first call. The same OAuth can be used for multiple API calls as long as it is not expired.

Access Error

The service authenticates and authorizes the client, and provides the following status codes when errors occur:

401 Unauthorized. The authorization credentials are either missing or incorrect. The caller has to provide the right credentials to be authenticated in order to access the service.
403 Forbidden. The request sent by the client was correct, but access to the resource identified by the URL is forbidden for some reason. The server understood the request, but is refusing to fulfill it.

Choose organization

Choose organization

Delete user