-
Notifications
You must be signed in to change notification settings - Fork 67
Basic Payment
Payment at the payment gateway is the basic and easiest way to pay at ČSOB payment gateway. After redirecting the customer to the payment gateway, the payment gateway will take care of the entire payment process and the merchant will only wait for the customer to return (by redirection) back to the e-shop.
After redirecting to the payment gateway, the customer can pay either with a payment card (enter its data - number, validity and CVC code), or choose Apple Pay / Google Pay wallets or ČSOB payment button. The choice of payment methods depends on the contract settings. If you feel that something is wrong or you want to offer your customers more payment methods, please contact [email protected].
If you open the payment gateway in a mobile application (Android / iOS), do not use WebView technology. For the full functioning of the payment gateway page in the application, use technologies that enable a fully functional and native display of the browser. We recommend Chrome Custom Tabs for Android, SFSafariViewController for iOS.
Card payment must be authenticated at the payment gateway using 3D Secure. After redirecting the customer to the payment gateway, the payment gateway will take care of the entire 3DS2 authentication process itself. We recommend that you provide as much as possible purchase metadata to increase the probability that the payment will be authenticated by the card issuer without confirmation.
Apple Pay payment is verified using Touch ID, Face ID or Apple Watch.
Google Pay is also verified using Touch ID or Face ID. In the case of using a card stored in a Google account (not in an Android wallet), the payment will be additionally verified using 3D Secure.
The ČSOB payment button is authenticated in online banking using the method used by the customer (typically ČSOB Smart Key).
By default, the customer has 30 minutes to complete a payment at the payment gateway. If you have a time-sensitive application (e.g. a reservation system) that requires payment to be made faster, you can shorten the payment time when creating a payment at the payment gateway (parameter in the payment/init
function).
After redirecting the customer to the payment gateway, you can continuously check the status of the payment using the payment/status
function. Unfortunately, it sometimes happens that the customer does not redirect back to the e-shop, even though the payment has been successfully completed and the order is paid. Therefore, we recommend that you always check the status of your payment thirty minutes after your redirection to the payment gateway (or after a shorter time if you set the allowed payment time to a lower value). You will find out the final status of the payment (paid / declined) regardless of the customer's return to the e-shop.
- Payment lifecycle
- Integration and API security
- Activation of the production environment
- Test cards and credentials
- API Sunset
- Payment Authentication
- Basic Payment
- OneClick Payment
- Custom Payment
- Apple Pay
- Google Pay
- Collecting partial card payment
- ČSOB Payment Button
- Payment Skip Pay
- API Integration
- Request Signing and Response Signature Validation
- API Methods Overview
- Basic Methods
- Methods for OneClick Payment
- Methods for Apple Pay
- Methods for Google Pay
- Methods for ČSOB Payment Button
- Methods for Skip Pay
- Purchase metadata