Payment Gateway Template
Best practices for recurrent payments Always get the customer’s consent with the recurrent payment before the transaction, not afterwards. Best practices for recurrent payments Always get the customer’s consent with the recurrent payment before the transaction, not afterwards. No transaction based on the template for recurrent payment has been performed in the past 12 months. When making the first payment, the customer agrees to have her/his card saved on the payment gateway (usually in a form of a checkbox that says “save my card for next purchases”). customer initiated recurring payment, but the transaction was later refunded as she/he returned the goods). As soon as the transaction is authorised, the customer is informed about successful payment in the last step of the merchant’s checkout. This transaction is a standard payment transaction (customer is redirected to the gateway, enters card details, completes the 3D-Secure authentication and the transaction is then authorised) and will be stored by the payment gateway as template for recurrent payment. However, the customer can ask her/his card issuer to stop the recurring. The cardholder asked his/her card issuer not to honour any recurrent payments initiated by the merchant.
Payment Gateway Template
Recurrent payment Ondřej Zaoral edited this page Dec 6, 2015 · 3 revisions Pages 25 Home Association & 3D Secure Acceptance Marks Credit Cards for Testing eAPI 1.5 eAPI 1.5 EN eAPI v1 (English version) eAPI v1 CZ FAQ: Features and Commercial Issues How to Switch to the Live Environment Interactions between the Customer and the Gateway in the most typical Situations Loga asociací a 3D Secure Logo obchodníka Merchant logo personalization Migration from GP Webpay Opakovaná platba Přechod do produkčního prostředí Přechod z již používané platební brány GP Webpay Recurrent payment Setting the colour scheme Stavy platební brány a komunikace s klientem (plátcem) Technical FAQ Testovací karty Změna barevného schématu brány Časté funkční a komerční dotazy Časté technické dotazy Show 10 more pages… Česky 1. On the other hand the transaction with remembered card is processed on the gateway. Merchant duties for recurrent payment execution When starting the recurrent payment (i.e. When the recurrent payment is not authorised, explain the situation and offer alternative. The value of the recurrent payment in the mobile channel is even higher than on desktop. The original transaction (template for recurrent payment) or any other following transaction is subject to a chargeback or other dispute initiated by the customer’s card issuer. And there is one more reason. Offer an alternative payment – one of them is a standard card payment (redirect to the gateway, use a new card). Integrace platební brány a e-shopu eAPI v1 eAPI v1.5 Opakovaná platba Testovací karty Loga asociací a 3D-Secure Nastavení vlastního barevného schématu Logo obchodníka Návod na přechod do produkčního prostředí Přechod z brány GP Webpay 2. You also need to secure your shop, i.e. Difference between the recurrent payment and card remembered on the gateway The recurring payment is processed without the need for the customer to enter CVC and pass 3D-Secure authentication again. creating the template for recurrent payment), the merchant needs to obtain customer consent (usually in a form of a checkbox that says “save my card for next purchases”). Always tailor this explanation. Should the transaction not be authorised, keep the customer in the loop. The second key difference is contractual. The original transaction (template for recurrent payment) has not been completely authorised, cleared and settled (e.g. Explain the customer value of the recurrent payment and explain that card data is saved with the bank, not your shop. It only simplifies payments for customers by showing them cards they used in previous purchases on the gateway. Gateway Integration eAPI v1 eAPI v1.5 Recurrent payment Credit Cards for Testing Association & 3D-Secure Acceptance Marks Setting the colour scheme Merchant logo personalization How to Switch to the Live Environment Migration from GP Webpay 2. In order to establish the recurrent payment for the customer, you need to tell this to the gateway when initiating the payment. Explain what happened and what the causes might be. The original transaction (template for recurrent payment) has not been completely authorised, cleared and settled (e.g. The subsequent transactions are way easier to pay – the customer just selects the “saved card” as payment option and the shop system executes the transaction call to the payment gateway – using the template for recurrent payment, without redirecting the customer. Gateway Integration eAPI v1 eAPI v1.5 Recurrent payment Credit Cards for Testing Association & 3D-Secure Acceptance Marks Setting the colour scheme Merchant logo personalization How to Switch to the Live Environment Migration from GP Webpay 2. The original transaction (template for recurrent payment) or any other following transaction is subject to a chargeback or other dispute initiated by the customer’s card issuer. “One click payment” is the most convenient payment on the mobile and solves one of the largest problems of m-commerce – cumbersome payments. Use recurrent payment actively on mobile webs and in apps. However, the customer can ask her/his card issuer to stop the recurring. There is no need to enter the card number and expiration date again, but the CVC needs to be entered and 3D-Secure authentication needs to be completed.
Payment Gateway Template
When does the ability to call recurrent payments end, or is cancelled? Your customer can not cancel the recurring payment (i.e. Časté dotazy (FAQ) Funkční a komerční dotazy Technické dotazy Stavy platební brány a komunikace s klientem English 1. The second key difference is contractual. As soon as the transaction is authorised, the customer is informed about successful payment in the last step of the merchant’s checkout. Offer an alternative payment – one of them is a standard card payment (redirect to the gateway, use a new card). When does the ability to call recurrent payments end, or is cancelled? Your customer can not cancel the recurring payment (i.e. Integrace platební brány a e-shopu eAPI v1 eAPI v1.5 Opakovaná platba Testovací karty Loga asociací a 3D-Secure Nastavení vlastního barevného schématu Logo obchodníka Návod na přechod do produkčního prostředí Přechod z brány GP Webpay 2. When the recurrent payment is not authorised, explain the situation and offer alternative. Watch 20 Star 26 Fork 4 csob/paymentgateway Code Issues 32 Pull requests 2 Wiki Pulse Graphs Recurrent payment Ondřej Zaoral edited this page Dec 6, 2015 · 3 revisions Pages 25 Home Association & 3D Secure Acceptance Marks Credit Cards for Testing eAPI 1.5 eAPI 1.5 EN eAPI v1 (English version) eAPI v1 CZ FAQ: Features and Commercial Issues How to Switch to the Live Environment Interactions between the Customer and the Gateway in the most typical Situations Loga asociací a 3D Secure Logo obchodníka Merchant logo personalization Migration from GP Webpay Opakovaná platba Přechod do produkčního prostředí Přechod z již používané platební brány GP Webpay Recurrent payment Setting the colour scheme Stavy platební brány a komunikace s klientem (plátcem) Technical FAQ Testovací karty Změna barevného schématu brány Časté funkční a komerční dotazy Časté technické dotazy Show 10 more pages… Česky 1. While the option of remembered cards is active automatically for all merchants, the recurrent payment is activated by ČSOB on a case-by-case basis. Merchant duties for recurrent payment execution When starting the recurrent payment (i.e. No transaction based on the template for recurrent payment has been performed in the past 12 months. recall the consent) on merchant’s e-shop pages. use SSL for all communication between the customer and the shop (not only on the checkout pages). Apart from the situation when the card expires, there are also other cases that result in the inability to execute further recurring transactions. Difference between the recurrent payment and card remembered on the gateway The recurring payment is processed without the need for the customer to enter CVC and pass 3D-Secure authentication again. And there is one more reason. customer initiated recurring payment, but the transaction was later refunded as she/he returned the goods). Customer does not leave the shop. Frequently asked Questions Features and Commercial Issues Technical questions Gateway – Customer Interactions Clone this wiki locally Clone in Desktop How to you recurrent payment and what it is actually good for Your returning customers can pay on “one click” with recurrent payment. creating the template for recurrent payment), the merchant needs to obtain customer consent (usually in a form of a checkbox that says “save my card for next purchases”). Value of recurrent payment is different for quick food delivery than when selling computers. The value of the recurrent payment in the mobile channel is even higher than on desktop. Explain the customer value of the recurrent payment and explain that card data is saved with the bank, not your shop. When making the first payment, the customer agrees to have her/his card saved on the payment gateway (usually in a form of a checkbox that says “save my card for next purchases”). Explain what happened and what the causes might be. Časté dotazy (FAQ) Funkční a komerční dotazy Technické dotazy Stavy platební brány a komunikace s klientem English 1. While the option of remembered cards is active automatically for all merchants, the recurrent payment is activated by ČSOB on a case-by-case basis. The subsequent transactions are way easier to pay – the customer just selects the “saved card” as payment option and the shop system executes the transaction call to the payment gateway – using the template for recurrent payment, without redirecting the customer. There is no need to enter the card number and expiration date again, but the CVC needs to be entered and 3D-Secure authentication needs to be completed.
Payment Gateway Template
The cardholder asked his/her card issuer not to honour any recurrent payments initiated by the merchant. recall the consent) on merchant’s e-shop pages. “One click payment” is the most convenient payment on the mobile and solves one of the largest problems of m-commerce – cumbersome payments. Use recurrent payment actively on mobile webs and in apps. It only simplifies payments for customers by showing them cards they used in previous purchases on the gateway. Always tailor this explanation. You also need to secure your shop, i.e. On the other hand the transaction with remembered card is processed on the gateway. Should the transaction not be authorised, keep the customer in the loop. Your client’s focus on shopping with you is stronger before the payment than after the payment (when everything is done). This transaction is a standard payment transaction (customer is redirected to the gateway, enters card details, completes the 3D-Secure authentication and the transaction is then authorised) and will be stored by the payment gateway as template for recurrent payment. use SSL for all communication between the customer and the shop (not only on the checkout pages). Frequently asked Questions Features and Commercial Issues Technical questions Gateway – Customer Interactions Clone this wiki locally Clone in Desktop How to you recurrent payment and what it is actually good for Your returning customers can pay on “one click” with recurrent payment. In order to establish the recurrent payment for the customer, you need to tell this to the gateway when initiating the payment. Apart from the situation when the card expires, there are also other cases that result in the inability to execute further recurring transactions. Customer does not leave the shop. Value of recurrent payment is different for quick food delivery than when selling computers. Your client’s focus on shopping with you is stronger before the payment than after the payment (when everything is done).