Payments API - sequence diagrams

Last updated: 16 June 2026 | Change log

Below are some common flows when using the Payments API.

For greater control of the payment flow, view the sequence diagrams for our Modular APIs.

Guest card payment

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.

Card payment with External 3DS, where authentication is completed by your own MPI or 3DS provider before the payment request is submitted.

Exemption granted with a placement of authorization and is honored by the issuer (payment authorized)

Setup a customerAgreement to store credentials for future CIT payments.

Set the customerAgreement.type to cardOnFile and storedCardUsage to first
Set tokenCreation.type to worldpay in order to store the credentials.
The example includes 3DS for SCA or 3DS mandated countries
If no initial payment is to be made (e.g. free trial), set the value.amount to 0. A card verification is performed instead.

Using a previously stored card to make a payment

Setup a customerAgreement to store credentials for future MIT payments.

Set the customerAgreement.type to subscription and storedCardUsage to first
Set tokenCreation.type to worldpay in order to store the credentials.
The example includes 3DS for SCA or 3DS mandated countries and has the threeDS.challenge.preference set to challengeMandated.
If no initial payment is to be made (e.g. free trial), set the value.amount to 0. A card verification is performed instead.

Send a Merchant Initiated Transaction (MIT) request for subsequent recurring transactions.