Custom Gateway: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
[[Category:Payments]]
[[Category:Payments]]
  ''This page is about the menu SETTINGS->PAYMENTS->PAYMENT GATEWAYS->CUSTOM GATEWAY''
[[Category:Payment_Gateways]]
<div class="heading">Custom Gateway</div>
  This page is about the menu SETTINGS->PAYMENTS->PAYMENT GATEWAYS->CUSTOM GATEWAY and explains how to connect with a payment gateway of your choice.


Required skills: html, programming
<span style="color: #f3e504; font-size: 250%;" >{{#fas:lightbulb}} </span> Required skills: html, programming
 
__TOC__
== Introduction ==
= Introduction =


You can create an interface to an external (not integrated) payment gateway.
You can create an interface to an external (not integrated) payment gateway.
Line 10: Line 12:
The booker will be shown a button which will take them to the specified URL with the value from "Post Data" included as an HTML POST.
The booker will be shown a button which will take them to the specified URL with the value from "Post Data" included as an HTML POST.


== Transfer to Custom Gateway ==
= Transfer to Custom Gateway =


The post data is sent to the custom gateway as if it came from a normal HTML form being submitted
The post data is sent to the custom gateway as if it came from a normal HTML form being submitted
Line 21: Line 23:




The custom gateway POST data is posted from the users browser when they click the pay button.
*The custom gateway POST data is posted from the users browser when they click the pay button.
This means the POSTED data will be visible in the page source code and should not contain any secret or private data.
*This means the POSTED data will be visible in the page source code and should not contain any secret or private data.


== Webhook to notify of payment status ==
= Webhook to notify of payment status =


A notify URL is available for the external gateway to report a successful collection of the deposit.
A notify URL is available for the external gateway to report a successful collection of the deposit.
Line 52: Line 54:
If there is any text content in the response, it will be an error message which means it was not successful.
If there is any text content in the response, it will be an error message which means it was not successful.


== Payment gateways with specific requirements ==
= Payment gateways with specific requirements =
 
The payment values can be first posted to your server.  
The payment values can be first posted to your server.  
Your server can process the data and convert it into the format required by the payment gateway.
Your server can process the data and convert it into the format required by the payment gateway.
Finally redirecting the guest to the payment gateway with the data in the required format.
Finally redirecting the guest to the payment gateway with the data in the required format.


Examples where this may be required are adding authorization headers or passwords or transforming the data into a specific format required by the payment gateway.
Examples where this may be required are adding authorization headers or passwords or transforming the data into a specific format required by the payment gateway.