Card based processing features
Our Acquiring API supports following functionalities.
Feature |
ECOM |
MOTO |
|---|---|---|
Final Authorization |
Yes |
Yes |
Pre-Authorization |
Yes |
Yes |
Pre-Authorization adjustments (Increments & Reversals) |
Yes |
Yes |
Account verification |
Yes |
Yes |
Strong Customer Authentication (3D Secure 2.x.x) |
Yes |
NA |
Strong Customer Authentication exemptions |
Yes |
NA |
Card-On-File - Cardholder Initiated & Merchant Initiated |
Yes |
Yes |
Dynamic Currency Conversion (DCC) |
Yes |
NA |
Authorization reversal |
Yes |
Yes |
Online capture |
Yes |
Yes |
Refunds (Referenced) |
Yes |
Yes |
Refunds (Standalone) |
Yes |
Yes |
Address verification |
Coming soon |
Coming soon |
Name verification |
Coming soon |
Coming soon |
Credit transfers |
Coming soon |
Coming soon |
Issuer installments |
Coming soon |
Coming soon |
Marketplace |
Coming soon |
NA |
Message flows in card transaction processing
In the realm of card, a financial transaction could be conducted in two ways - Single Message or Dual Message processing flow. The distinction between single message and dual message processing flows significantly impacts the authorization and settlement of card transactions. Understanding the characteristics of these two processing flows is essential for effectively managing and orchestrating card transactions within your platform. All major card schemes supports these messaging flow and so Worldline.
Single message processing
In a single message processing, the authorization & the clearing requests are combined and sent as a single API request to us thus reducing the complexity of the transaction flow on your end. However, single message flows may limit the ability to
modify the authorized amount after the initial request, as the clearing amount is typically predetermined at the time of authorization.
reverse a transaction as the clearing takes places in a shorter window of time post authorization.
Dual message processing
In contrast, with dual message processing, the authorization and the clearing requests are sent as two distinct API requests to us. The initial authorization request seeks approval for the transaction amount without immediately initiating the clearing process, providing flexibility to adjust the authorized amount before the final settlement or even reverse it. The subsequent clearing/capture request confirms the completion of the transaction and triggers the transfer of funds from the cardholder's account to the merchant's account, based on the previously obtained authorization.
We have listed the most common use cases that can be achieved using Single and Dual message processing. This would serve as an overview of best practices for each of them.
Payments
Operation |
Type (Conceptual) |
Request |
ECOM |
POS |
|---|---|---|---|---|
Single messaging operations |
||||
Initial |
Yes |
Coming soon |
||
Dual messaging operations |
||||
Initial |
(Final & Pre-Authorization) |
Yes |
Coming soon |
|
Follow-up |
Yes* |
Coming soon |
||
(Part or Full) |
Yes** |
Coming soon |
||
(Part or Full) |
Yes |
Coming soon |
||
* This is applicable for Pre-Authorization only.
** Reversal of final authorizations for Mastercard transaction isn't recommended as it would incur additional fees
Refunds
Operation |
Type (Conceptual) |
Request |
ECOM |
POS |
|---|---|---|---|---|
Single messaging operations |
||||
Initial |
(Part or Full)¤ |
Yes |
Coming soon |
|
Yes |
Coming soon |
|||
Dual messaging operations |
||||
Initial |
(Part or Full)¤ |
Yes |
Coming soon |
|
Yes |
Coming soon |
|||
Follow-up |
Yes |
Coming soon |
||
Yes |
Coming soon |
|||
¤ Though the referenced refund operation is marked as an initial operation in the above table, it is technically a follow-up operation of a captured purchase transaction.
Generic operations
You can perform following operations depending on your business or platform needs using our Acquiring API. These are independent of messaging flow and environment/channel agnostic.
Type (Conceptual) |
Request |
|---|---|