The Online Payments solution of CCV is constantly evolving and improving to provide users with the best possible experience. It is designed to streamline the payment process, making it convenient and efficient for both customers and businesses. On March 22nd 2023, a new version was released which brings important additions to our suite of payment tools, and we are excited to offer it to our users. We believe that this new release will be a valuable addition to the Online Payments solution of CCV.
More information about CCV Online Payments can be found here: https://www.ccv.eu/en/solutions/payment-services/ccv-online-payments/
Seamless return to bank app from CCV payment page
Customers can now complete their payments on CCV’s payment page seamlessly by using their bank app to scan a QR code. Without this feature, the payment experience ends with the CCV “thank you” page after the transaction is finished, and the users must manually navigate back to the bank app. With this new feature, bank apps can integrate the new “originator” parameter, which allows it to automatically reopen after the payment is finished. This provides a seamless and efficient payment experience for customers, eliminating the need for manual navigation. The availability of this feature may vary among different banks, depending on whether or not they integrated this feature.
Thank you page
The CCV Online Payments payment page now includes a default “thank you” page for payment transactions initiated through a QR code or link, making it especially useful for payment QR codes that are displayed on invoices. When the payment page is opened from a webpage, a “return URL” can be provided in the API, which will redirect the customer to the specified URL once the payment is complete. However, when no return URL is present, such as in the case of a payment link scanned from an invoice, the default thank you page will be displayed instead.
For all transaction requests made to the API endpoint “/api/v1/payment”, if there is no returnURL provided, the system will search for the transaction reference. If the reference is found, the thank you page will display the transaction details. If the reference is not found, a default thank you page will be presented. The first image illustrates how the thank you page appears when the transaction reference is found, while the second image displays the default thank you page when the reference is not found.
Bugfix: Bancontact WIP API timeout
The Bancontact WIP API previously experienced a timeout issue when the parameter “userAuthenticationMethods” was not included in the Vault payment API request. With the implementation of this bugfix, the API will now return a “400 Bad Request” error message instead.
For more information about the Bancontact WIP API, please refer to https://redirect.jforce.be/api/v1/doc/bancontact.