In this section:
Table of Contents | ||||
---|---|---|---|---|
|
Definition
A Refund is a process that credits a Cardholder account from the Merchant account.
It is initiated in case of reimbursement of a payment transaction, totally or partially.
A Refund performed at the POI (Point-of-Interaction) does not have to be linked to a previous payment transaction.
Reference Documents
Nexo-Fast Specification Update Bulletin No. 11 Reference to the Original Transaction for Refund
Processing
The Refund service can be performed and processed in two ways:
Offline Refund | The Refund transaction is accepted or decline by the Acceptor without requesting an authorization from the Acquirer. At the end of the transaction or later in time, the Acceptor might send a completion to notify the Acquirer of the outcome of the transaction. |
Online Refund | An authorisation is sent by the Acceptor to the Acquirer to request the approval of the transaction. An online authorisation exchange is made up an AcceptorAuthorisationRequest message used to request the authorisation of the related transaction and an AcceptorAuthorisationResponse message used to provide the outcome of the authorisation. |
Refund with Reference Data
In general the Refund Service can be performed without reference to an original transaction.
However, when a Refund is initiated from a sale system or a device control (eg. MerchantApp), the payment system can optionally receive an initial transaction reference in order to fill in the corresponding data elements in the Refund message (see Nexo-Fast Specification Update Bulletin No. 11 Reference to the Original Transaction for Refund for more information).
Refund Reference Data may be identical to the Reference Data of the original Service, but this is not mandatory and not checked. Refund Reference Data is not used to retrieve the transaction data of the original Service, but it is stored in the transaction database for the Refund.
Configuration
Enable Refund Service
To enable the Refund Service:
Define the Refund Service proprieties in the Service Settings Table (E4).
Payment networks usually recommended to protect the Refund Service. The Refund Service can be protected by using the
'DF10' - Service Settings[1, 5] = 1b (Service protected)
. If the Refund Service is protected, the POI will request the merchant code entry before allowing the transaction.
Add the Refund Service in the list of configured service in Terminal Data (E1) using:
'DF13' - Configured Services[1, 7] = 1b (Refund)
or'DF67' - Configured Services Extended[1, 7] = 1b (Refund)
or
.
Setting Refund processing mode (Offline or Online)
The Refund Service processing mode is configurable per Application Profile (E6) through the 'DF27' - Application Profile Settings(APS) [2, 2]
.
Offline Refund Settings
To support Offline Refund, set 'DF27' - Application Profile Settings(APS) [2, 2] = 0b
.
Online Refund Setting
To enable Online Refund, set 'DF27' - Application Profile Settings(APS) [2, 2] = 1b (Refund online)
.
Arkos API
See Amadis Developers' Guide page on Refund Service for more information.
Sequence Diagrams
Standalone POI
Online Refund with Refund Reference Data
In general the Refund Service can be performed without reference to an original transaction.
However, when a Refund is initiated from a sale system or a device control (eg. MerchantApp), the payment system can optionally receive an initial transaction reference in order to fill in the corresponding data elements in the Refund message (see Nexo-Fast Specification Update Bulletin No. 11 Reference to the Original Transaction for Refund for more information).
Refund Reference Data may be identical to the Reference Data of the original Service, but this is not mandatory and not checked. Refund Reference Data is not used to retrieve the transaction data of the original Service, but it is stored in the transaction database for the Refund.
Refund Reference Data provided by a Sale SystemInfo |
---|
Refund Reference Data is optional. Merchant may use the RecepientTransactionID returned by the Acquirer in the original transaction (see new Jira improvement) |
Offline Refund with Refund Reference Data
Connected POI
Refund
15.00$
Notes:
User shall be able to press “OK” to skip Refund Reference Data Entry
Refund
15.00$
Present Card
Refund
15.00$
Approved
Welcome / Bienvenue
Receipt
The payment receipt shall include the Refund Reference Data.Note |
---|
Nexo Retailer V3The Refund Reference Data of the payment transaction to pay back shall be specified in the PaymentRequest through the |
OriginalPOITransaction.POITransactionID.TransactionID
as follows:title | PaymentRequest with PaymentType = "Refund" |
---|
Code Block |
---|
<OriginalPOITransaction>
<POITransactionID TransactionID="1234567890" TimeStamp="2020-01-01T18:00:00.1+01:00"/>
</OriginalPOITransaction> |
The Refund Reference Data will be transmitted to the acquirer host as follows:
Expand | ||
---|---|---|
| ||
|
Refund Reference Data provided by a Device Control (eg. MerchantApp)
See Refund Service to provide Refund Reference Data from a Device Control.
Message Examples
Online Refund with no Refund Reference Data
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Expand | ||
---|---|---|
| ||
|
Online Refund with Refund Reference Data
Expand | |||||
---|---|---|---|---|---|
| |||||
|
Expand | ||
---|---|---|
| ||
|
Offline Refund with no Refund Reference Data
Expand | ||
---|---|---|
| ||
|
Offline Refund with Refund Reference Data
Expand | ||
---|---|---|
| ||
|
MerchantApp Considerations
UI/UX (Recommended)
Sales
Purchase
Refund
Cancellation
Reference :
1234567890ABC
1 2 3 4 5 6 7 8 9 0
q w e r t y u i o p
a s d f g h j k l
z x c v b n m . :
Maj Space Sym
|
Note |
---|
The protection of the Refund Service is outside of the current scope in connected POI mode. |