Documentation v1.0.0

Get Started

Before you can integrate a SmartFastPay product or solution, you must set up your development environment to get OAuth 2.0 client ID and secret credentials for the sandbox and live environments. You exchange these credentials for an access token that authorizes your REST API calls. To test your web and mobile apps, you create sandbox accounts

Logging into the Developer Dashboard to get credentials and create sandbox accounts requires a developer, personal, or business account. Each account provides different levels of access to API functionality.

Capabilities Developer Account Personal Account Business Account
Access sandbox x x x
Send and receive money x x
Go live x x

Get credentials

To generate REST API credentials for the sandbox and live environments:

  1. Log in to the Developer Dashboard with your SmartFastPay account.
  2. Under the MANAGEMENT menu, select Credentials.
  3. Make sure you're on the Sandbox tab to get the API credentials you'll use while you're developing code. After you test and before you go live, switch to the Live tab to get live credentials.

Get an access token

Your access token authorizes you to use the SmartFastPay REST API server. To call a REST API in your integration, exchange your client ID and secret for an access token in an OAuth 2.0 token call. While there are a few ways to get a token, here are examples using both the Postman app and a cURL command.

Your own environment's HTTP library or function may have username and password fields or an auth parameter in which you pass your client ID and secret. You can also add your Base64 encoded client ID and secret in an Authorization: Basic header.

Make REST API calls

In REST API calls, include the URL to the API service for the environment:

  • Sandbox:
  • Live:

Also, include your access token to prove your identity and access protected resources.

This sample call, which shows the Transaction creates, includes a bearer token in the Authorization request header. This type of token lets you complete an action on behalf of a resource owner.

                                                        curl -v --location --request POST '' \
                                                            --header 'Content-Type: application/json' \
                                                            --header 'Authorization: Bearer < Access-Token >' \
                                                            --data-raw '{
                                                                "customer_id": "58f0c005-3b7d-4c75-81f3-93b9a6fee864",
                                                                "branch": "Office 2",
                                                                "name": "Richard Roe",
                                                                "amount": 4300,
                                                                "currency": "USD",
                                                                "callback": "",
                                                                "transaction": {
                                                                    "id": "b08e3897-6505-4bb4-81a5-6e3a1d29e277",
                                                                    "redirect": {
                                                                        "url": "",
                                                                        "type": "URL"

The response shows the page or url, choosed by redirect type:

                                                            "requestId": "73eaaecf-1bf4-4847-b4a9-8c615e891e1b",
                                                            "data": {
                                                                "url": "",
                                                                "transaction_id": "f834fc1b-c8a0-4613-bcc9-2c188f6ef180"