Registrar usuarios finales mediante API

Register end users in D1 to link cards to an end user.

This is a backend-to-backend flow between your issuer backend and the D1 backend.

When end user registration is required

End user registration depends on how you use D1:

• Card creation model: Register the end user before you create any card in D1.

• Card registration model: End user registration can be:

  • Explicit, via the D1 API, or

  • Implicit, during card creation or card registration (based on consumerId).

Define consumerId

Your issuer backend provides a consumerId for each end user. D1 uses it to identify the end user. It is used in the D1 API, D1 SDK, and D1 portal.

consumerId must not contain personal information. Do not include name, email address, phone number, PAN, or similar data.

Choose a registration model

Choose whether the D1 backend stores end user personal information. This choice changes your registration flow.

Store personal information in the D1 backend

Use this model when you want D1 to store personal information. D1 can then cache the data. This reduces calls to your issuer backend.

You must provide the mandatory fields in personalInformation.

You must keep D1 up to date when personal information changes.

Consumer registration flow between the issuer backend and the D1 backend

Do not store personal information in the D1 backend

Use this model when D1 must not store personal information.

You can still register the end user explicitly without personalInformation.

You can also skip explicit registration. Rely on implicit registration during card creation or card registration.

When D1 needs personal information, it calls your issuer backend. For example, it can do this for Tokenization.

If you already use Register Consumer 1.0, you can keep using it. Use Register Consumer 2.0 for new integrations.