Register end users and cards in D1

Register end users, accounts, and cards before you use D1 services.

Registration is an issuer backend to D1 backend flow. You can register a card at any time before you use it with a D1 service.

Your issuer backend provides your own identifiers:

• consumerId for the end user

• accountId for the account

• cardId for the card

These identifiers are used to reference resources in the D1 API and during troubleshooting.

You may this flow if you use Tokenization v1 only.

The D1 API uses the term consumer for an end user. This documentation uses end user, and keeps API field names as-is (for example, consumerId).

Registration flow

End user and card registration flow (issuer backend to D1 backend)

Choose identifiers

If your issuer backend does not manage accounts (or you do not have a stable accountId), use consumerId as accountId.

Follow these rules for identifiers:

• Ensure consumerId, accountId, and cardId are unique in your D1 tenant.

• Do not include personally identifiable information (PII) in consumerId or accountId.

• Do not include sensitive card data (for example, PAN) in cardId.

Register an end user with cards

Call Register Consumer with cards from your issuer backend.

To add more cards for an existing end user, call the same API again. Reuse the existing consumerId, and include the new cards in the payload.

Legacy v1 registration APIs

These endpoints remain available if you integrated before Register Consumer with cards was released:

• Register Consumer

• Register Account

• Register Card