Decoupled amount
1. Introduction
The introduction of the PSD2 guideline requires you to meet new challenges, but also offers you new opportunities.
One of them is the possibility to process different amounts during the authentication (the 3-D Secure check) and the authorisation (blocking the funds on your customers’ credit card) step. This decoupled amount feature allows you to
- Delay / partially split shipments
- Increment an authorised amount
When your customer authenticates an amount higher than the authorisation, you can capture the additional amount(s) later - without renewing the authentication for this additional amount.
In contrast to classic recurring payment you are better protected against chargebacks as long as the additional amount(s) do not exceed the authenticated amount.
To capture these additional amount(s) you still have to tokenise the initial transaction with the full amount to be authenticated.
Have a look at typical use cases and how they implement this new feature.
and integration mode Server-to-server
2. Understand use cases
The need to process different amounts during the authentication/authorisation might happen in situations like these:
- Delayed/Partially split shipment: You want to offer your customers goods/services for a trial period. Alternatively, some goods/services are not available at the time of the order. Finalise/ charge the delivery at a later point – but your customers will not have to visit you store and authenticate themselves again!
- Increment an authorised amount: You want to add a margin to a base amount, as the final amount you want to charge eventually is either equal or higher at the time of the order. Think of booking a hotel room in advance, but you have to charge more on the final invoice because of additional services during the stay. There is no need for a separate transaction to cover this margin: simply authenticate the order for the maximum amount (base amount + margin) and charge anything between the base and the maximum amount later
Learn now how to implement either scenario in your customers’ payment journey.
3. Initiate order
To use this feature, you need to process your transactions in two steps:
- Send a standard CreatePayment with 3-D Secure at the time of the initial order
- Finalise the order via a standard CreatePayment
This chapter covers the first step. Refer to the dedicated chapter for the second step.
Once you want to initiate an order, send the CreatePayment request with the following properties:
| Properties | Remarks |
|---|---|
|
order.amountOfMoney.amount cardPaymentMethodSpecificInput
|
Depending on use case, send the following values:
A typical request looks like this: |
4. Finalise order
Once you want to finalise the order, send a standard CreatePayment request with these properties: