Skip to content
APIs
/
Payments
/
Use Cases
/
Subsequent recurring payment

Last Updated: 15 July 2025 | Change Log

Subsequent recurring payment

Following an initial agreement, make subsequent recurring payments.

The request must contain:

"customerAgreement": {
    "type": "subscription", 
    "storedCardUsage": "subsequent" 
}

1. Basic Request

The schemeReference must be provided to link the first and subsequent recurring payment.

{
    "transactionReference": "Memory265-13/08/1876",
    "merchant": {
        "entity": "default"
    },
    "instruction": {
        "method": "card",
        "paymentInstrument": {
            "type": "plain",
            "cardNumber": "4000000000001091",
                "expiryDate": {
                "month": 5,
                "year": 2035
            }
        },
        "customerAgreement": {
            "type": "subscription",
            "storedCardUsage":"subsequent",
            "schemeReference": "MCCOLXT1C0104"
        },
        "narrative": {
            "line1": "trading name"
        },
        "value": {
            "currency": "GBP",
            "amount": 42
        }
    }
}

View the full API Request schema

2. Add additional features

Risk Assessment

We assess the payment for fraud before proceeding with authorization.

Enterprise
Worldpay eCommerce

Auto Settlement

Automatically settle a payment following the authorization.


Enterprise
Worldpay eCommerce

Account Funding Transactions (AFT)

Transfer funds from a card account to another destination, rather than for the provision of goods or services.

Enterprise

Financial Service (MCC 6012/6051)

For domestic Financial Services providers (MCC 6012) based in the Visa Europe Region, you must supply this additional data.

Enterprise

Latin America Installments

Fulfill a one-time installment charge, to allow the customer's acquirer bank collecting the payments over time.

Enterprise

Payment Facilitator

Facilitate transactions on behalf of your sub-merchants.

Enterprise

Account Updater

Automatically update card details to prevent declines due to expired or changed cards.

Enterprise

3. Response

Features that change the API flow

Certain features add additional requests and responses:

  • FraudSight - you may receive a 201 - fraudHighRisk outcome, stopping the payment
  • Auto Settlement - automatic 202 - sentForSettlement following authorization.
    • If any of the AVS/CVC response riskFactors are marked as notMatched the payment will be sentForCancellation automatically by default but can be disabled.
application/json
No response example

View the full API Response schema