Skip to main content
An External Card is a debit, prepaid or credit card belonging to a Counter Party, used as the destination for a push style card payout.

Two ways to add a card

If you aren’t PCI DSS Level 1 certified, use an External Card Session instead of calling the Card API directly - contact HIFI if you’re unsure which applies to you.

Counterparty requirements

The counterparty must be ACTIVE, and have the following accepted fields set in addition to its own minimum, before you can add an external card for them:
If a required field is missing, HIFI rejects the request with ACTION_NOT_ALLOWED (422) - update the counterparty with the missing field and retry.
The counterparty doesn’t need to be created upfront if the card is added through an External Card Session submission, since the session’s own schema already enforces these fields. Otherwise, you can also pass counterpartyId as an optional fields when creating the session.

Supported Card Network

Add an external card via API

Registers a card directly against an existing counterparty. Requires an Idempotency-Key header. cardNumber and cvv are used once to tokenize the card with HIFI’s card provider and are never returned in the response. Request
Response

Deactivate an external card

Revokes a previously-added card. A deactivated card can no longer be used as a payout destination, but its record and history are preserved. Request
Response

Retrieve a counterparty’s external cards

List a counterparty’s registered cards Request
Response

External Card Sessions

An External Card Session is the hosted alternative to the Card API - the required path if you aren’t PCI DSS Level 1 certified. Instead of your backend collecting the card number, the recipient types their own card and identity details directly into a HIFI-hosted page, so raw card data never touches your servers. You generate a session and get back a hosted URL; HIFI’s hosted page collects the counterparty and card details from there and creates both once the recipient submits.

Generate a session

requestId is a client-supplied UUID that makes the call idempotent. If counterPartyId is omitted, the recipient enters their own counterparty details as part of the hosted flow; if provided, only card details are collected. Set recipientEmail to have HIFI email the hosted link directly to the recipient. Request
Response
Retrieving or submitting a session directly from your own backend isn’t supported - that’s handled entirely by the hosted page. Subscribe to EXTERNAL_CARD and COUNTER_PARTY webhook events to know when the resulting resources are created.

Getting Help

  • 📧 Email: support@hifi.com
  • 💬 Slack: Message us in our shared Slack channel