Deferred Payments
Use the deferred-payment indicator when creating an eligible Checkout or Payment Link pre-authorisation. The indicator tells the payment gateway to process the transaction as a deferred payment. It is intended for use cases where the final amount is not known when the customer begins the payment journey, such as electric-vehicle charging.
Before you begin
You need an existing Checkout or Payment Link integration that can create a PRE-AUTH transaction. Continue to use the standard payment-page redirect, webhook, redirect-back URL, transaction-status, and completion flows for your integration.
This feature does not add a field to the payment page. It does not change the Checkout session response, inquiry response, or post-processor output.
Add the deferred-payment indicator
Set transactionType to PRE-AUTH and send true in order.orderDetails.deferredPayment.
| Field | Type | Required | Value and behavior |
|---|---|---|---|
order.orderDetails.deferredPayment | boolean | No | Set to true to request deferred-payment processing for a PRE-AUTH transaction. |
| Transaction type | deferredPayment value | Gateway behavior |
|---|---|---|
PRE-AUTH | true | Sends the deferred-payment indicator for gateway processing. |
PRE-AUTH | false, null, or omitted | Does not activate deferred-payment processing. |
| Any other transaction type | Any value | The indicator is not used for deferred-payment processing. |
The gateway validates the request and applies the deferred-payment treatment supported by your configuration. A request can still be declined or rejected by the acquirer, issuer, or card-scheme rules.
Checkout request example
Add the indicator to your normal Checkout or Payment Link request. Replace the placeholder values and URLs with values from your integration.
{
"storeId": "{{storeId}}",
"merchantTransactionId": "{{uniqueMerchantTransactionId}}",
"transactionOrigin": "ECOM",
"transactionType": "PRE-AUTH",
"transactionAmount": {
"total": 22.00,
"currency": "EUR",
"components": {
"subtotal": 20.00,
"vatAmount": 2.00
}
},
"order": {
"orderDetails": {
"deferredPayment": true
}
},
"checkoutSettings": {
"locale": "en_GB",
"webHooksUrl": "https://merchant.example/payment-webhook",
"redirectBackUrls": {
"successUrl": "https://merchant.example/success",
"failureUrl": "https://merchant.example/failure"
}
},
"paymentMethodDetails": {
"cards": {
"authenticationPreferences": {
"challengeIndicator": "01"
}
}
}
}
Checkout creation response
A successful request creates a Checkout session. Redirect the customer to checkout.redirectionUrl to continue the payment journey.
{
"checkout": {
"storeId": "12341457997",
"checkoutId": "TSmHLn",
"redirectionUrl": "https://www.checkout-lane.com/#/?checkoutId=TSmHLn"
}
}
This response confirms only that the Checkout session was created. It is not proof that the pre-authorisation was approved, completed, or settled. Determine the final outcome through your normal redirect, webhook, and transaction-status handling.
Troubleshooting
| Symptom | What to check |
|---|---|
| Checkout request is rejected before the customer is redirected | Confirm the request uses transactionOrigin: "ECOM", transactionType: "PRE-AUTH", and a boolean deferredPayment: true. Confirm that deferred payment is enabled for the store. |
| The indicator has no effect | Confirm that it is nested at order.orderDetails.deferredPayment, is the JSON boolean true, and is sent only with PRE-AUTH. |
| The payment is declined after submitting card payment | Check the merchant configuration, payment method, acquirer route, and applicable issuer or card-scheme rules with Fiserv. |
Updated about 2 hours ago