v1.2 | February 11, 2024
- Added the functionality to authorize and/or cancel Alternative Forms of Payment (AFOP), e.g., PayPal, UnionPay, NAPAS.
API Information
Format
JSON
Current Version
1.2
Environment
Production
What's New
- Added the functionality to authorize and/or cancel Alternative Forms of Payment (AFOP), e.g., PayPal, UnionPay, NAPAS.
v1.1 | December 12, 2023
- Added functionality to authorize payment with ApplePay. There are two ways to perform such authorization: 1) Sending cavv, eci, and paymentType values within the digitalWallet object and associating it with the respective paymentMethod Object (code, type, number, expirationDate, securityCode are required), 2) Including the cryptogram and paymentType values within the digitalWallet object and associating it with the corresponding paymentMethod object (code and type are required).
- Added functionality to cancel authorization for ApplePay. If authorization is performed with cavv, eci, cancel request must include the same digitalWallet and paymentMethod data as in the original authorization request. If authorization was performed with cryptogram it is essential not to include the digitalWallet node. Instead, a basic creditCard payment method must be sent without card details, as the user has no access to them. Card details will be taken from cache based on paymentReference.
- Added functionality to fulfill booking with authorization performed with ApplePay. If authorization was performed with cavv, eci - fulfillment request looks same as when the authorization is performed with regular Credit/Debit Card. If authorization was performed with cryptogram fulfillment request should have PaymentMethod object only with type filled. No card details should be sent, as the user has no access to them. These values will be taken from cache based on paymentReference.
API Information
Format
JSON
Current Version
1.1
Environment
Production
What's New
- Added functionality to authorize payment with ApplePay. There are two ways to perform such authorization: 1) Sending cavv, eci, and paymentType values within the digitalWallet object and associating it with the respective paymentMethod Object (code, type, number, expirationDate, securityCode are required), 2) Including the cryptogram and paymentType values within the digitalWallet object and associating it with the corresponding paymentMethod object (code and type are required).
- Added functionality to cancel authorization for ApplePay. If authorization is performed with cavv, eci, cancel request must include the same digitalWallet and paymentMethod data as in the original authorization request. If authorization was performed with cryptogram it is essential not to include the digitalWallet node. Instead, a basic creditCard payment method must be sent without card details, as the user has no access to them. Card details will be taken from cache based on paymentReference.
- Added functionality to fulfill booking with authorization performed with ApplePay. If authorization was performed with cavv, eci - fulfillment request looks same as when the authorization is performed with regular Credit/Debit Card. If authorization was performed with cryptogram fulfillment request should have PaymentMethod object only with type filled. No card details should be sent, as the user has no access to them. These values will be taken from cache based on paymentReference.
v1.0 | August 16, 2023
- Initial release.
API Information
Format
JSON
Current Version
1.0
Environment
Production
What's New
- Initial release.