Below are some common flows when using the Payments API.
- Guest card payment
- FraudSight
- 3DS
- SCA exemptions
- Storing credentials for future CIT - Worldpay and Network Tokens
- Storing credentials for future MIT - Worldpay and Network Tokens
For greater control of the payment flow, view the sequence diagrams for our Modular APIs.
A basic card payment with no additional features such as 3DS or FraudSight enabled.
Card payment with FraudSight enabled that results in a highRisk assessment outcome that stops the payment.
Card payment with 3DS authentication enabled, resulting in a frictionless issuer response.
Setup a customerAgreement to store credentials for future CIT payments. Create a Worldpay Token in order to store the credentials. For SCA or 3DS mandated countries 3DS authentication should also take place.
Setup a customerAgreement to store credentials for future MIT payments. Create a Worldpay Token in order to store the credentials. For SCA or 3DS mandated countries 3DS authentication should also take place and have the challenge.preference set to challengeMandated.