Omni-Channel
Omni-Channel is the fusion of, the previously separated, POS (Point Of Sales) and E Commerce, enabling the merchant to move transactions between these two worlds, starting them on one end, finishing them on the other, or just moving card-data from the POS-side to E Commerce.
Requirements
The following requirements need to be met, in order to use omni-channel:
A capable Saferpay licence (Flex, E Commerce, or Business) and thus the existence of a valid identification with a username and password for the Saferpay system.
Availability of at least one active Saferpay terminal via which payment can be carried out and availability of the associated Saferpay TerminalId.
Availability of at least one POS-device and a corresponding contract, that is compatible with Worldline Omni-Channel.
If the Secure Card Data use-case is used, you also need Saferpay Secure card Data to be activated.
Omni-Channel can only be performed with the following payment methods:
UnionPay (Creation of an alias is NOT SUPPORTED!)
Twint (Creation of an alias is NOT SUPPORTED!)
WeChat Pay (Creation of an alias is NOT SUPPORTED!)
The Transaction-Reference
Before you can begin integrating the specific use-cases, you first need to acquire the Transaction Reference.
This reference is used to perform the omni-channel requests in the first place, by referencing a previously performed POS (or E Commerce) transaction inside the Worldline acquiring-systems. Using this reference, the transaction and/or used card-details then can be transfered from the POS system to Saferpay (E Commerce).
How to get the transaction reference, using Saferpay.
Saferpay always returns the reference inside the Transaction.SixTransactionReference parameter:
How to get the transaction reference via POS
The transaction-reference may always have this general format:
However, depending on which POS integration you have, this information may not be obvious, or even be returned in multiple parameters, requiring you to first combine a certain set of parameters, in order to get this reference.
When in doubt, please contact your account-manager/sales contact, or POS-support. They'll be able to help you.
Use-Cases
Once you have ensured, that the transaction reference is gathered and built correctly, you can proceed with integrating the specific Omni-Channel use-cases, which are the following:
Transferring a transaction from POS to Saferpay (E Commerce)
This enables you to perform further actions on a POS transaction, like authorizing a card and capturing the transaction on E Commerce side, or refunding a POS transaction via Saferpay, be it via Backoffice, or via API.
This is done, by executing the OmniChannel AcquireTransaction request:
Request
Response
This then behaves like any other Saferpay transaction, offering the same set of possibilities. The transaction will also show up inside the Saferpay Backoffice Journal.
Transferring the card-details from POS to Saferpay (E Commerce)
This method gathers the card-details of a POS transaction and saves them within Saferpay Secure Card Data, giving you a card-alias. This alias then can be used like any other Secure Card Data alias. You could perform recurring payments, or even offer this card within the card holders online account, so he/she may execute further transactions, without having to enter his/her card-details.
This is done, by executing the OmniChannel InsertAlias request:
Request
Response
This gives you a Secure Card Data alias, which can be used like any other alias.
Testing
Testing Omni-Channel requires a special activation and configuration of your test-account. For end-to-end testing, you'd also require special POS-devices and test-cards.
If you are in need of testing Omni-Channel use-cases, please contact your account-manager/sales contact, in order for the activation to be done and to get access to the needed hardware.
Last updated
Was this helpful?