Custom Gateway: Difference between revisions

Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 22: Line 22:
A special template variable [PAYMENTAMOUNT] will contain the value of the deposit when booking and the value of the payment request when used for payment requests.
A special template variable [PAYMENTAMOUNT] will contain the value of the deposit when booking and the value of the payment request when used for payment requests.


'''Example''': <code> deposit=[PAYMENTAMOUNT]&bookid={BOOKID]</code> will post fields deposit and bookid to the external gateway.
'''Example''': <code> deposit=[PAYMENTAMOUNT]&bookid=[BOOKID]</code> will post fields deposit and bookid to the external gateway.


*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.
Line 41: Line 41:
The notify will add the deposit to the booking invoice and trigger updates to booking status and email notifications to guest and host.
The notify will add the deposit to the booking invoice and trigger updates to booking status and email notifications to guest and host.


The notify must post a key field with a value that matches to setting and contain at least 6 characters.
The notify must post a key value that matches the value in the key setting and contain at least 6 characters.


The data should be sent as HTML POST form data
The data should be sent as HTML POST form data
Line 56: Line 56:
These POST fields are optional:
These POST fields are optional:


<code>status</code> = booking status, 0 (cancelled), 1 (confirmed), 2 (new), 3 (request)
<code>status</code> = booking status, 0 (cancelled), 1 (confirmed), 2 (new), 3 (request) or -2 (nochange)


<code>amount</code> = amount of the deposit collected
<code>amount</code> = amount of the deposit collected