Get details for a specific credit card

This Tango API endpoint retrieves detailed information about a specific registered credit card on your platform. It is typically used to verify card metadata such as the last four digits, expiration date, status, associated account, activation timestamp, and any configured funding‑confirmation contacts. To retrieve the card record, you must provide the token returned when the credit card was originally registered.

Use case

Acme Health is a digital healthcare platform that allows clinics and medical providers to purchase patient‑care supplies, pay for service subscriptions, and fund wellness incentive programs. Each clinic stores one or more company credit cards within Acme Health’s portal. Acme Health uses this Tango API endpoint to:

• Validate the correct clinic is using the card. Many clinics are supported under this platform.
• Ensure the card is active before auto‑funding wellness accounts. Some cards may be expired or disabled by admin.
• Display card information in the Acme Health clinic portal.
• Keep clinic account teams informed by sending notification to the card contacts.
• Maintain a clear trail for audit and compliance workflow.

Endpoint

Use the following endpoint to get details for a specific credit card.

Parameters

The following path parameters is required when calling this endpoint:

Response body

Tango uses the provided token to find the correct card and returns all metadata associated with it—not the full card number. The credit card details are used to verify that a card is active or expired, check who owns the card (customer/account), view the last four digits, manage contact emails for funding confirmations, and apply your own access rules based on customer/account relationships.

This is especially useful if your platform has multiple customers, multiple accounts, or restricted permissions, since you can know exactly which account and customer a particular card is linked to.

On a successful request (200 OK), the response body includes the following fields:

Examples

The following payload is an example for when you get credit card details:

{
  "customerIdentifier": "string",
  "accountIdentifier": "string",
  "token": "string",
  "label": "string",
  "lastFourDigits": "string",
  "expirationDate": "string",
  "status": "string",
  "createdDate": "2025-02-14T17:56:23.295Z",
  "activationDate": "2025-02-14T17:56:23.295Z",
  "contactInformation": [
    {
      "fullName": "string",
      "emailAddress": "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: