-
Notifications
You must be signed in to change notification settings - Fork 67
Activation of the production environment
To transition from an integration to a production environment, the merchant must perform the following test scenarios.
The following tests are performed on the integration environment (https://iapi.iplatebnibrana.csob.cz
). These tests differ from the free tests you performed during development only by the use of specific card numbers.
- call the
echo
operation using theGET
method - check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(0)
- call the
echo
operation using thePOST
method - check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(0)
- perform the payment initialization (
payment/init
) and the subsequent redirection to the payment gateway (payment/process
) - use the test card # 4000007000010006, any valid expiry and CVC 100. Submit the payment. This will result in a successful payment authentication and authorization and redirect back to the e-shop. Check that you returned to the shop on the desired page.
- check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(0),paymentStatus
(4 or 7 depending onclosePayment
settings for the transaction)
- perform the payment initialization (
payment/init
) and the subsequent redirection to the payment gateway (payment/process
) - click the"Cancel payment and return to the shop" button
- check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(0),paymentStatus
(3)
- perform the payment initialization (
payment/init
) and the subsequent redirection to the payment gateway (payment/process
) - do NOT enter any card details, do NOT submit the payment and wait for 30 minutes for the automatic redirect back to the e-shop. You can alternatively close the window and call
payment/status
after 30 or more minutes) - check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(130),paymentStatus
(6)
- perform the payment initialization (
payment/init
) and the subsequent redirection to the payment gateway (payment/process
) - use the test card # 4000007000010006, any valid expiry and CVC 100, submit the payment which will be authorized and you will be redirected to the shop
- check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(0),paymentStatus
(4 or 7 depending onclosePayment
settings for the transaction) - perform
payment/reverse
operation for the particular transaction you just did - check the response code (200 OK)
- check the signature of the response (using the key for the integration environment)
- in the returned JSON response - check
resultCode
(0),paymentStatus
(5)
As soon as you are done with all the scenarios, please confirm the completion in the ČSOB POS Merchant portal. This confirmation will submit your test cases for account readiness review.
After checking the successful completion of the tests, we will inform you about the activation of the production environment. From now on, you can make actual payments and collect money from customers. Don't forget to perform the following steps:
- reconfigure URL to the payment gateway API from the integration environment (
https://iapi.iplatebnibrana.csob.cz/
) to the production payment gateway (https://api.platebnibrana.csob.cz/
). - check that the merchant's private key (used for request signing) is configured on the production environment
- check that the payment gateway's public key (used for response signature verification) is configured on the production environment
- in case of applepay@shop is used by merchant the Apple Pay production configuration has to be used (i.e. merchantID, Apple Pay processing certificate etc., see description of Apple Pay payment method)
- in case of googlepay@shop is used by merchant the Google Pay production configuration has to be used (see description of Google Pay payment method)
We also recommend performing a production test before making payments available to clients. You can use any working credit card you normally use. You can, of course, return this test transaction afterwards.
- 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