- METHOD TYPEVoucher
- PAYMENTS
- PAYOUTS
- REFUNDS
- RECURRING
Introduction
Abon allows customers to make online payments in a simple and secure way, just like paying in cash. At more than 200,000 locations in Europe, the customer purchases an Abon voucher. Then, the customer uses a 16-digit code on the voucher to make a payment on your website.
Supported Countries
- Austria
- Belgium
- Bosnia
- Bulgaria
- Croatia
- Cyprus
- Czech Republic
- Denmark
- Estonia
- Finland
- France
- Germany
- Greece
- Hungary
- Ireland
- Italy
- Kosovo
- Latvia
- Lithuania
- Luxembourg
- Macedonia
- Montenegro
- Malta
- Netherlands
- Poland
- Portugal
- Romania
- Serbia
- Slovakia
- Slovenia
- Spain
- Sweden
Supported Currencies
- BAM
- BGN
- CZK
- DKK
- EUR
- HUF
- MKD
- PLN
- RON
- RSD
- SEK
Payment (Deposit) Flow
Follow these steps to perform a payment using Nuvei REST API integration:
1. Generate a sessionToken
Press here for details.
2. Send a /payment
Request
Perform the payment by sending a /payment
request with its mandatory parameters including:
userTokenId
– Unique customer identifier in merchant system.amount
Ifamount
=”0“, the payment amount is the value of the voucher.
Otheramount
values are validated against the amount of the voucher. If they match, the payment is accepted. Otherwise, it is rejected.currency
paymentOption.alternativePaymentMethod
class containing:paymentMethod
: “apmgw_Abon“,abon_voucherNumber
: “<Abon 16-digit voucher number>”
deviceDetails
class containing:ipAddress
billingAddress
class containing:firstName
,lastName
,email
,address
userDetails
class containing:firstName
,lastName
,email
,address
- Germany –
phone
required - Italy –
identification
required
- Germany –
Example /payment
Request
{ "sessionToken":"<sessionToken from /getSessionToken>", "merchantId":"<your merchantId>", "merchantSiteId":"<your merchantSiteId>", "clientRequestId":"<unique request ID in merchant system>", "amount":"102", "currency":"EUR", "userTokenId":"<unique customer identifier in merchant system>", "clientUniqueId":"<unique transaction ID in merchant system>", "paymentOption":{ "alternativePaymentMethod":{ "paymentMethod":"apmgw_Abon", "abon_voucherNumber": "<16-digit voucher number>" } }, "deviceDetails":{ "ipAddress":"<customer's IP address>" }, "billingAddress":{ "firstName":"John", "lastName":"Smith", "email":"[email protected]", "country":"BE" }, "userDetails":{ "firstName":"John", "lastName":"Smith", "email":"[email protected]", "country":"BE" }, "timeStamp":"<YYYYMMDDHHmmss>", "checksum":"<calculated checksum>" }
Abon processes the transaction and returns a transaction notification and status.
Example /payment
Response
{ "internalRequestId": 913985339, "status": "SUCCESS", "errCode": 0, "reason": "", "merchantId": "4273555827014385119", "merchantSiteId": "222058", "version": "1.0", "clientRequestId": "20240212132854", "sessionToken": "103fe11e-06b2-4af7-b494-724b44bc4e8b", "clientUniqueId": "20180327175242", "orderId": "420274599", "userTokenId": "TestToken2", "paymentOption": { "userPaymentOptionId": "104082698", "card": {} }, "transactionStatus": "PENDING", "transactionId": "711000000032057913" }
After the transaction is processed, Nuvei sends a Direct Merchant Notification (DMN) that includes the result of the transaction to urlDetails.notificationUrl
, which Nuvei recommends including in the /payment
request.
User Experience
- The user buys an Abon voucher.
In Italy, the user provides an identification number. - On your payment page, the user selects the Abon payment method and enters the 16-digit Abon voucher number.
- The user must accept the terms and conditions to make the payment.
- Optional steps:
- If you are integrating Abon using our Payment Page and do not offer an open amount, the APM provider makes sure the Abon voucher amount is the same as the provided amount. If the amounts do not match, the payment request is declined.
- In Germany, the user authenticates and confirms the Abon transaction using the Abon mobile app.
- In Italy, the APM provider makes sure the identification value the user provides on the payment page matches the identification number the user provided when buying the voucher.