Fund an account

Use the following endpoint to fund an account on your platform:

Endpoint	Description
`POST {URI}/creditCardDeposits`	Fund an Account.

The following body parameters are used to send data with this endpoint. 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.

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

When you use this endpoint to make a funding call, one of the following funding statuses are returned:

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 `amountCharged` in the response. 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

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": [
    {}
  ]
}

The possible response codes for this endpoint are as follows. For details, see i18nkey codes and their error messages:

200 OK
400 Bad request
401 Unauthorized
403 Forbidden
409 Conflict, Duplicate Exists
500 Internal Server Error
503 Service Unavailable