Omnichannel

Introduction

Today, customers experience a brand and not a channel within a brand. They shop both online and in-store, and sometimes, this applies to one single purchase.

Imagine the following scenario:

1. Your customers pay a deposit for a product in-store which is out of stock
2. You send the product to your customers as soon as it is available and request the payment for the remaining amount online
3. Later, your customers inform you that the product is unfortunately defective, asking to return the product. After receiving the returned product, you refund the product online

This example shows how these cross-linking of online/in-store activities prove to be a tremendous challenge for merchants: You need to keep track of all these steps to ensure a correct order system and a satisfactory customer experience.

Our Omnichannel solution will ease your implementation by

• Providing a seamless customer journey
• Giving you a single and unified view of your customers' interactions

Omnichannel groups all operations under one single order, in one chain of action – regardless of whether they happen in-store or online!

Implement Omnichannel

Omnichannel allows the following maintenance operations:

• Subsequent sales
• Refunds/payouts

Process subsequent sales

The first initial transaction marking the beginning of the chain of actions can be either an in-store (via your point-of-sale terminal) or online transaction (via our API).

If you process this initial transaction online, make sure to add
unscheduledCardOnFileRequestor="cardholderInitiated"
unscheduledCardOnFileSequenceIndicator="first"
to your request. This will ensure you comply to the Credentials-On-File regulation (COF) when processing the subsequent transaction.

To process subsequent transactions, send a request to our dedicated SubsequentPayment endpoint:

{
   "subsequentCardPaymentMethodSpecificInput":{
      "authorizationMode":"SALE"
   },
   "order":{
      "amountOfMoney":{
         "amount":3000,
         "currencyCode":"EUR"
      }
   }
}

Property	Description
{paymentId}	The payment.Id of the first transaction (either instore or online) for which you process a new subsequent payment. Add it as a path to the SubsequentPayment endpoint URL
subsequentCardPaymentMethodSpecificInput. authorizationMode	Set to either "FINAL_AUTHORIZATION"/"PRE_AUTHORIZATION"/"SALE" depending on whether you want to process payments in (pre)authorisation/direct sale mode
order.amountOfMoney      amount      currencyCode	amount: The gross amount you want to charge for this order currencyCode: The ISO 4217 currency code for this amount

Process refunds/payouts

Add the following properties to a standard RefundPayment request:

{
   "amountOfMoney":{
      "amount":100,
      "currencyCode":"EUR"
   }
}

Property	Description
{paymentId}	The payment.Id of the first transaction (either instore or online) for which you request a refund Add it as a path to the RefundPayment endpoint URL
order.amountOfMoney      amount      currencyCode	amount: The gross amount you want to charge for this order currencyCode: The ISO 4217 currency code for this amount

Sometimes you might want to refund more than the amount of the first initial transaction. We have a dedicated endpoint for these kind of requests.

Add the following properties to a standard CreatePayout request:

{
   "amountOfMoney":{
      "amount":1000,
      "currencyCode":"EUR"
   },
   "omnichannelPayoutSpecificInput":{
      "paymentId":"paymentId.id"
   }
}

Property	Description
omnichannelPayoutSpecificInput.paymentId	The payment.Id of the first transaction (either instore or online) for which you request a payout
order.amountOfMoney      amount      currencyCode	amount: The gross amount you want to payout for this order currencyCode: The ISO 4217 currency code for this amount