Merchant Enrollment

Certain services require merchant acceptors to be enrolled for merchants to be able to make use of them. We provide the Create Enrollment endpoint for this. The following services are currently available for merchants to enroll with:

Enrollment is generally an asynchronous process, meaning that the initial result is a pending state, whereas the definitive enrollment state will be known at a later point in time. You can query the current status of your enrollments by invoking the Get All Enrollments endpoint.

There is a known latency from Mastercard ISSM indicating that it can take up to 24 hours for Mastercard to synchronize the merchant enrollment status in the Directory Server (DS). We suggest retrying the 3DS charge/authentication later. If the same error persists even after 24 hours of successful enrollment, please contact us. Example request:

When enrolling merchants for Mastercard SCOF through our endpoint, we in turn use the Mastercard Checkout Solutions API - Registration to complete this process. However, this is a batch-wise process where we submit the merchant details and an SRCiDPAID per merchant. We continuously query the Mastercard systems to determine whether the batch has been processed successfully. Once we get a 'completed successfully' status, the enrollment has been completed, and this will also be reflected in our systems. Once the enrollmentStatus is equal to 'enrolled,' the enrollment key can be used to tokenize cards.

Enrollment is generally an asynchronous process, meaning that the initial result is a "pending" state, whereas the definitive enrollment state will be known at a later point in time. You can query the current status of your enrollments by invoking the Get Enrollments endpoint.

The merchant identifier for Mastercard is called the DPA and is required for merchants to be able to request network tokens with Mastercard.

For SCOF enrollments, the programType should be merchant_obo. We do support commerce_platform_obo technically, but enabling this functionality requires alignment with Mastercard.

For Visa VTS, a similar enrollment process is followed, which is performed via the Visa Digital Solutions API - Onboarding. This is also a batch-wise process, and there is some delay between the initial registration and the confirmation that this has been completed successfully. Once the enrollmentStatus is equal to 'enrolled,' the enrollment key can be used to tokenize cards. Here is an example request:

The merchant identifier for Visa is called the TRID and is required for merchants to be able to request network tokens with Visa.