CIT/MIT Compliance guide - Worldpay for Platforms eDDR

To become CIT/MIT compliant when integrating the Worldpay for Platforms eDDR, there is a small additional change that will be required which include an additional field in the initial eDDR API request.

• The Worldpay for Platforms eDDR can also apply 3DS for further security. Depending on your integrated payment flows it will require little or no development on your end.

To begin testing and development, your Sandbox account will need to be configured accordingly. Please reach out to your Partner manager to get started.

Worldpay for platforms CIT/MIT compliant eDDR flowchart

The flowcharts below demonstrates the typical API flow of the Worldpay for Platforms eDDR:

• Worldpay for Platforms eDDR (3DS not applicable).pdf

• Worldpay for Platforms eDDR (3DS applicable).pdf

Please note, additional fields required for 3DS including the CIT/MIT compliant additions, should you have 3DS enabled and applicable to your integration.

API steps for CIT/MIT compliant Worldpay for Platforms eDDR

1 additional field required in the eDDR API request:

• POST Generate eDDR Token

  • Additional field:

    • CardAuthorizationType:

      • Possible values below:

        • RECURRING

        • INSTALMENT

        • UNSCHEDULED

All other steps remain the same, however a detailed API step-by-step guide is provided below:

The process for using the eDDR token is simply:

1. Call the POST Generate eDDR Token to obtain a token and a redirect URL.

   1. Specify CardAuthorizationType:

      1. RECURRING

      2. INSTALMENT

      3. UNSCHEDULED

   2. Minimum payer details:

      1. First name

      2. Last name

      3. Email address

2. Redirect the end user to the URL you received with the token.

3. After the end user has completed the form we will redirect them back to your website using the returnURL you provided when generating the token.

   1. If the end user enters card details as the desired payment method, this will trigger the mandatory 3DS validation and the end user will be redirected to complete the 3DS challenge. Once the 3DS challenge is complete, the end user will be redirected back to the returnURL you specified in the original request.

   2. The redirection back to the returnURL is the notification trigger for your software to identify that the eDDR page has been completed.

4. Call the Token Lookup API endpoint to obtain the result of the token.

5. Schedule single or multiple payments:

   1. POST Schedule a single payment

   2. POST Schedule multiple future payments

6. Determine result of scheduled debit - GET Search for transaction status change

7. Remove transaction from data set - POST Acknowledge transaction status change

Bank Account details for testing

Test Bank Account Details

Test Bank Account Details - NZ specific

Test Cards to test different cases