Payment Web Application changelog

1.53

2024-01-25

• UIADDED From this version the Payment Web App supports the VA Payment payment method flow for KRW payments. For more information see Payment methods of the Payment Web Application guideline.

1.52

2024-01-12

• UIADDED Added new currencies GHS, KES and NGN. From this version the Payment Web App supports the Offline Bank Transfer payment method for NGN payments and Mobile Money payment method for GHS and KES payments. For more information see Payment methods of the Payment Web Application guideline.

1.51

2023-12-12

• UIADDED Added new Payment Method Pay Me for Capitec Bank’s customers . From this version the Payment Web App supports the Pay Me payment method flow. For more information see Payment methods of the Payment Web Application guideline.

1.50

2023-11-22

• UIADDED From this version the Payment Web App supports new RedirectURL query parameter productId - identification of a product related to a payment order. For more information see Initial redirect of the Payment Web Application guideline.

1.49

2023-09-19

• UIADDED Added new PHP currency. From this version the Payment Web App supports the Offline Bank Transfer and QR Ph payment methods for PHP payments. For more information see Payment methods of the Payment Web Application guideline.

• UIADDED Added new Payment Method Capitec Pay . From this version the Payment Web App supports the Capitec Pay Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

1.48

2023-06-09

• UIADDED Added new LAK currency. From this version the Payment Web App supports the Offline Bank Transfer payment method flow for LAK payments. For more information see Payment methods of the Payment Web Application guideline.

1.47

2023-05-30

• UIMODIFIED From now on your channel name won’t be shown to customer if GET /merchant-info is not included in Get an authorization token request.

1.46

2023-04-12

• UIADDED Added new Payment Method E-Wallet . From this version the Payment Web App supports the E-Wallet Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

1.45

2023-02-17

• UIADDED Offline Bank Transfer payment method now supports displaying of QR code to customer to provide more convinient way of completing a payment by simply scanning a QR code. Currently a QR code is provided only for payments in VND currency.

1.44

2023-01-13

• UIADDED Added new ZAR currency. From this version the Payment Web App supports the Instant Bank Transfer and Offline Bank Transfer payment methods for ZAR payments. For more information see Payment methods of the Payment Web Application guideline.

• UIADDED From this version the Payment Web App supports new RedirectURL query parameter showDeepLink which enables possibility for your customer to proceed with the payment with just one click instead of e.g. downloading and uploading of a QR code in UPI QR payment method flow on mobile device. For more information see Initial redirect of the Payment Web Application guideline.

1.43

2022-10-20

• UIADDED From this version the Payment Web App supports the Offline Bank Transfer payment method flow for THB payments. For more information see Payment methods of the Payment Web Application guideline.

1.42

2022-10-17

• UIADDED Added new KRW currency. From this version the Payment Web App supports the Offline Bank Transfer payment method flow for KRW payments. For more information see Payment methods of the Payment Web Application guideline.

1.41

2022-05-27

• UIADDED Added new Payment Method Viet QR . From this version the Payment Web App supports the UPI QR Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

1.40

2022-05-02

• UIMODIFIED New attribute upiQrDeepLink in the UPI QR payment page.

  • To improve user experience of our UPI QR payment flow we introduced UPI QR deeplink which allows your customer to open UPI QR compatible payment app and initiate their payment with just one click. Instead of complicated downloading and uploading QR code on the mobile device to pay with the app your customer just opens the link and his payment is ready to be sent.

1.39

2022-04-11

• UIADDED Added new JPY currency. From this version the Payment Web App supports the Offline Bank Transfer payment method flow for JPY payments. For more information see Payment methods of the Payment Web Application guideline.

1.39

2022-04-07

• UIADDED Added new Payment Method Crypto Offline.

• UIADDED From this version the Payment Web App supports the UPI QR Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

1.38

2022-03-15

• UIADDED Added new Payment Method UPI QR . From this version the Payment Web App supports the UPI QR Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

Integration DEMO Web Application

2021-12-07

• NEW We launched our Integration DEMO Web Application which will smartly and transparently show you how easy and effective integration with us is. Go to this page and try it.

1.37

2021-09-15

• UIREMOVED removed Bank Name attribute from the P2A_VA payment page.

1.36

2021-12-01

• UIADDED Added new Payment Method DuitNow QR. From this version the Payment Web App supports the DuitNow QR Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

1.35

2021-11-04

• UI Now Payment Web Application validates emailAddress and phoneNumber coming from the payment web application RedirectURL when your customer submits the payin payment.

  Check If you use payment methods where the emailAddress and phoneNumber are required or can be collected and you relay on your system to collect them and provide them in the RedirectURL, make sure that their format follows the validation rules from the RedirectURL request definition.

1.34

2021-09-07

• UI Now Payment Web Application shows your channel name configured in the Home page in the Merchant Channel Setup widget. This improvement improves your customer experience as your customer is informed about you during whole payment flow in the Payment Web Application.

  • UI Merchant information setup is available in your Merchant Back-office Sandbox or Live account merchant account on the Home page in the Merchant Channel setup widget.

  • ADDED To authorise Payment Web Application to obtain the Merchant Channel Name you have to add GET /merchant-info endpoint to POST /auth-tokens request, for more detail about the Auth token see our Fine-grained privileges section.

  In case that the Payment Web Application is not authorized to obtain Merchant Information or the data has not been configured yet then Payment Web Application simply hide the affected elements and proceed with the payment flow.

1.33

2021-09-07

• UIADDED Added new Payment Method QRIS (QR Code Indonesian Standard). From this version the Payment Web App supports the QRIS Payment method flow. For more information see Payment methods of the Payment Web Application guideline.

  QRIS is a payment method intended for the Indonesian market which allows users of wallets which support QRIS to pay using scanning QR codes.

1.32

• ADDED Payment option selection step control

  You can now control whether your Customer may choose a Payment option in our Payment Web App or It allows your Customer to use only the Payment option provided by you in the Payment Web App RedirectURL.

  • URLADDED Optional parameters paymentMethodCode and paymentOperatorCode have been added into the Payment Web App RedirectURL so that You can provide Payment option You want your Customer to use.

  • URLADDED Optional boolean parameter optionsAvailable has been added into the Payment Web App RedirectURL so that You can control whether Payment Web App allows your Customer to change Payment option you provided

  See these two Payment Web App scenarios to fully understand the feature - Scenario 4. Payment Web App flow - Payment option is selected by Customer in Merchant system and Scenario 5. Payment Web App flow - Payment option is selected by Customer in Merchant system but can be changed in the Payment Web App.

• ADDED Customer data collection step control

  You can now control whether a Payment Web App allows your Customer to collect or modify his data which we need to process and to manage your Payment orders.

  • URLADDED Optional parameters accountName, accountNumber, emailAddress has been added into the Payment Web App RedirectURL so that you can provide these your customer data from your system.

  • URLADDED Optional boolean parameter allowCustomerDataChange has been added into the Payment Web App RedirectURL so that You can control whether Payment Web App allows your Customer to change the data you provided.

  See these two Payment Web App scenarios to fully understand the feature - Scenario 2. Payment Web App flow - Customer data, we need to process and manage your Payment orders, are collected by Merchant system and Scenario 3. Payment Web App flow - Customer data are collected by Merchant system but can be changed in the Payment Web App.

1.0

This is the base version of the Payment Web Application.