Activation of the production environment - csob/paymentgateway GitHub Wiki
To transition from an integration to a production environment, the merchant must perform the following test scenarios.
⚠️ If you are interested in the way how to test during development within an integration environment, please check out use of test cards and simulating various transaction scenarios. These cards are not usable in a production environment.
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.
Communication test - echo (GET)
- 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)
Communication test - echo (POST)
- 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)
Successfully authorised payment
- 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)
Payment cancelled by the customer
- 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)
Expired payment (timeout)
- 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)
Payment reversal
- 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)
Confirm the execution of all test cases and submit for review
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.
Activation of the production approach
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)
Production test
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.