Custom Payment

Custom payment allows the customer to pay on the payment gateway such purchases during which he/she does not go through the typical e-shop purchase process. The merchant initiates the payment on the payment gateway. Consequently, the merchant obtains a payment link which is then delivered to the customer in the best way at this particular moment - by e-mail, SMS or as a QR code printed on the invoice. After opening the payment link, the customer can pay with all payment methods active on the merchant‘s payment gateway.

Custom payment is available on the ČSOB payment gateway since eAPI version 1.8 which adds support for payments initiation as well as payment links obtaining.

When should I use the Custom payment?

Of course, you can let your imagination, as well as your business needs, run wild. So, there are just a few suggestions for the Custom payment:

• when issuing invoices or advance invoices
• in case of need to pay when calling the client at the call centre
• when you need to receive a payment from a client for an additional order change that has caused a higher price

And then there is one more case: if you do not have any e-shop and you do not want to implement eAPI payment gateways into your internal systems (e.g. to serve clients in the call centre). The Custom payment can also be initiated "manually" in the ČSOB POS Merchant administration system. The result will be again a payment link with which your client pays - and does not realize at all that the payment was made manually.

How does the Custom payment work for my e-shop / system?

If you know how much a client should pay, you initiate a transaction on the payment gateway. In addition to the information, you send to the gateway when making "normal" payments (amount, your order number for pairing, details to display in your cart, etc.), you can also set a Custom payment validity at a rate of up to 60 days. After this time, the payment will no longer be active. From the gateway, you will get a payment link (in eAPI customerCode) that identifies the payment for your customer. The code is six-digit and it contains both numbers and letters. This completes the communication with the gateway and now you have to deliver the payment link to the customer in the form of https://platebnibrana.csob.cz/zaplat/{customerCode}. We do not limit the delivery method. It depends on your use of the Custom payment, whether you send the code by e-mail, SMS, invoice and whether you send it as a link or, for example, as a QR code.

When the customer opens a payment link, they see the payment gateway as if they were redirected from the e-shop. The customer can use all payment methods (i.e. choose between card and payment buttons directly on the gateway). Once the payment is completed, the customer is redirected to the e-shop which will then learn about the payment result. The payment link is active until its expiry date (max. 60 days, see above for setting up a payment) or payment of the transaction - whichever comes first. If the customer opens the payment link by chance or by mistake or the payment is declined, the payment link is still valid and the customer can return to the payment until the payment link expires.

If you create the Custom payment manually in ČSOB POS Merchant app, you can also choose a payment option without returning to the e-shop. This option is suitable if you have no system integrated with the payment gateway and the customer has nowhere to "return". You must then manually check the paid transactions in ČSOB POS Merchant.

Custom payment authentication

At the moment the payment link is opened by the customer, the authentication takes place in the same way as for a common basic payment. When creating Custom payment, the payment gateway must be provided with the same Purchase metadata as for the common basic payment.

How do we implement the Custom payment?

The Custom payment requires no new API methods. Served only by advanced extended parameters of payment/init methods. You will receive the handover code as part of your payment/init call response.

Custom payment and the Electronic Sales Registration function

Of course, if you use the ESR payment gateway function (supported only in API 1.7 and 1.8), you can also use the Custom payment. As in other cases, revenue will be reported immediately after the payment authorization. In other words, the gateway does not report any revenue for the Custom payment which is potentially awaiting payment for tens of days. You will receive data for the ESR receipt in the same way as you would for regular transactions, i.e. together with the transaction result information.

What else to know about the Custom payment?

What are the fees?

Same as for payment when redirecting the customer from the e-shop. There is no extra charge for the Custom payment.

How do I get the Custom payment?

We will enable you to make the Custom payments at your request. Please contact [email protected].