Fund an account
This Tango endpoint enables you to add funds to a specific Tango account using a credit card. This is currently the only funding method supported via the API. Funding an account via ACH, wire, and check deposits can only be done through the Tango portal.
Use case
Acme Health, a nationwide healthcare organization, runs multiple reward programs—one for employee wellness, one for patient engagement, and another for internal training incentives. Each program has its own Tango account, allowing Acme Health to track spending and maintain separate budgets. The Employee Wellness Program is about to launch a quarterly challenge, and thousands of $25 digital rewards will be issued. Before sending any rewards, Acme Health needs to ensure the “Wellness‑East” account has sufficient funds. To do this, the platform triggers the Tango API’s Fund an Account endpoint.
Endpoint
Use the following endpoint to fund an account on your platform using a credit card:
| Endpoint | Description |
|---|---|
POST {URI}/creditCardDeposits | Fund an Account. |
When funding an account using a credit card, you must ensure that the transaction is processed correctly and securely, using the appropriate body parameters.externalRefID is an idempotent field used to prevent accidental transfer duplication. It ensures that the same transfer is not processed multiple times. The externalRefID is returned in the funding response, funding details, and funding history.
Parameters
Body parameters are required in this endpoint to give specific, structured information to correctly process a credit‑card funding transaction. Each piece of data in the body tells Tango what to fund, for whom, with what card, for how much, and how to safely track the transaction.
The following body parameters are used to send data with this endpoint:
| Body params | Data type | Requirement | Description |
|---|---|---|---|
customerIdentifier | string | required | Specify the customer associated with the credit card. It must be the customer the accountIdentifier is associated with. The string must have 5-100 characters. |
accountIdentifier | string | required | Specify the account this credit card is associated with. The string must have 5-100 characters. |
externalRefID | string | optional | Specify the external reference ID to associate with this funding action. This value must be unique. Duplicate externalRefID is blocked at the account level. If a duplicate externalRefID is submitted, the funding request fails showing a 409 error message: “externalRefID is not unique. Duplicate funding request.” |
creditCardToken | string | required | Specify the credit card token to fund with. The string must have 40 characters. |
| amount | string | required | Specify the amount to fund in USD. |
Funding status
Funding status refers to the state of a credit‑card funding transaction after you call this endpoint (POST {URI}/creditCardDeposits) in the Tango API. It tells you where the funding request is in its lifecycle, whether the card has been charged, and whether the funds have been applied to the account.
There are three possible funding statuses:
Status | Description | Authorization | Account balance update | Charged |
|---|---|---|---|---|
Success | The funding transaction has successfully completed and funds have been applied to the specified account. | Yes | Yes | Yes |
Pending | The deposit has been received but the processing is not completed yet. It may be subject to review by Tango. While an authorization has been requested from the issuing bank, a capture/settlement has not yet occurred, and therefore the credit card has not yet been charged, as indicated by It may take up to three business day for pending deposits to complete processing and transition status. | Yes | No | No |
Declined | The funding transaction did not complete successfully and funds were not applied to the account. The credit card was not charged. If you need assistance, contact your Customer Success Manager (CSM) at [email protected] for help. | Yes* | No | No |
Examples
The following example response is returned when you use this endpoint to fund your account:
{
"referenceDepositID": "string",
"amount": 0,
"amountCharged": 0,
"feePercent": 0,
"createdDate": "2025-04-30T16:03:34.300Z",
"status": "string",
"externalRefID": "string",
"accountNumber": "string"
}Here's an example payload for when you receive an error:
{
"timestamp": "2025-02-21T23:23:13.930Z",
"requestId": "string",
"path": "string",
"httpCode": 0,
"httpPhrase": "string",
"i18nKey": "string",
"message": "The error message will show here for error codes ",
"errors": [
{}
]
}Response codes
The possible response codes for this endpoint are as follows. For details, see i18nkey codes and their error messages:
| Response code | Meaning |
|---|---|
| 200 | The request was successful. |
| 400 | The server could not understand the request due to invalid syntax. |
| 401 | Authentication is required and has either not been provided or failed. |
| 403 | The server understood the request but refuses to authorize it. |
| 409 | The request could not be completed because it would cause a conflict with the current state of the resource. |
| 500 | Something went wrong on the server, but the server cannot be more specific about what the exact problem is. |
| 503 | The server is currently unable to handle the request due to temporary overload or maintenance. |
Updated 1 day ago
