Stripe Security Deposit capture: Difference between revisions
Jump to navigation
Jump to search
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
[[Category:How to]] | [[Category:How to]] | ||
[[Category:Payments]] | [[Category:Payments]] | ||
<div class="heading">Stripe - Authorise a Refundable Security Payment</div> | <div class="heading">Stripe - Authorise a Refundable Security Payment</div> | ||
This page is about the menu {{#fas:cog}} (SETTINGS) PAYMENTS > PAYMENT GATEWAYS > STRIPE and authorisation of a refundable payment | This page is about the menu {{#fas:cog}} (SETTINGS) PAYMENTS > PAYMENT GATEWAYS > STRIPE and authorisation of a refundable payment and explains how to setup a pending payment to ‘Capture/Authorise’ a refundable Security Deposit. | ||
__TOC__ | __TOC__ | ||
| Line 23: | Line 22: | ||
With Stripe you can authorise a payment on a credit card to be released after a fixed period if the payment is not collected. | With Stripe you can authorise a payment on a credit card to be released after a fixed period if the payment is not collected. | ||
You can define the Due date/time and the amount to be authorised. | You can define the Due date/time and the amount to be authorised. | ||
=Set up= | =Set up= | ||
== | <div class="mw-collapsible mw-collapsed"> | ||
<div class="headline-collapse" > | |||
Step 1: Setup Stripe Account | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
Go to {{#fas:cog}} (SETTINGS) PAYMENTS > PAYMENT GATEWAYS > STRIPE and set: | Go to {{#fas:cog}} (SETTINGS) PAYMENTS > PAYMENT GATEWAYS > STRIPE and set: | ||
| Line 39: | Line 43: | ||
*'''Title''' - Customise the title for this payment option. | *'''Title''' - Customise the title for this payment option. | ||
*'''Instruction''' - Create an optional description to appear next to the Stripe pay now button. | *'''Instruction''' - Create an optional description to appear next to the Stripe pay now button. | ||
</div></div> | |||
== | <div class="mw-collapsible mw-collapsed"> | ||
<div class="headline-collapse" > | |||
Step 2: Create a Payment Rule - Capture Refundable Security Deposit | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
Go to {{#fas:cog}} (SETTINGS) PAYMENTS > PAYMENT RULES | Go to {{#fas:cog}} (SETTINGS) PAYMENTS > PAYMENT RULES | ||
| Line 56: | Line 65: | ||
*All Booking Info Codes (optional) | *All Booking Info Codes (optional) | ||
*Exclude Booking Info Code= BOOKINGVIRTCARD, EXPEDIACOLLECT, AGODACOLLECT If you have virtual credit cards from the channels, then use this option. | *Exclude Booking Info Code= BOOKINGVIRTCARD, EXPEDIACOLLECT, AGODACOLLECT If you have virtual credit cards from the channels, then use this option. | ||
You will need to send a payment request link to the guest for them to authorise the payment as it is not possible to authorise a refundable payment on a Virtual Card. | |||
<span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} </span> You will need to send a payment request link to the guest for them to authorise the payment as it is not possible to authorise a refundable payment on a Virtual Card. | |||
Payment Action : | Payment Action : | ||
*Funding Source = Guest card only | |||
*Payment value adjustment = Default | |||
*Capture = NO - Authorised for collection later | *Capture = NO - Authorised for collection later | ||
*Add info code on success = add a Booking Info item to the booking on success | *Add info code on success = add a Booking Info item to the booking on success | ||
*Add info code on failure = add a Booking Info item to the booking on failure | *Add info code on failure = add a Booking Info item to the booking on failure | ||
Prevent Auto Payment : | Prevent Auto Payment : | ||
*Prevent payment if booking status : Cancelled | *Prevent payment if booking status : Cancelled | ||
*Prevent payment after check-out (days) = 7 (default) | |||
*Prevent payment action : Set Manual | *Prevent payment action : Set Manual | ||
</div></div> | |||
== | <div class="mw-collapsible mw-collapsed"> | ||
<div class="headline-collapse" > | |||
Step 3: Create Auto Actions | |||
</div> | |||
<div class="mw-collapsible-content"> | |||
Go to {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS | Go to {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS and click '''Create New Action''' to create them. | ||
If the guest credit card is already at Stripe. | |||
'''Auto Action 1 - Authorise payment for all bookings - Guest Credit card at Stripe''' | |||
For bookings via your booking page (direct) and Channel bookings (non virtual cards), the credit card has been sent and stored at Stripe. | For bookings via your booking page (direct) and Channel bookings (non virtual cards), the credit card has been sent and stored at Stripe. | ||
Trigger tab: | Trigger tab: | ||
| Line 90: | Line 101: | ||
**Time Window = 1 day | **Time Window = 1 day | ||
*Booking Source | *Booking Source | ||
**Booking Source = | **Booking Source =All (this will apply to all bookings, direct, manual and channels). If you want to have different auto actions/rules for direct bookings -v- channel bookings, then select ‘Direct’ this will include manually created bookings and booking page bookings. | ||
If you want to have different auto actions/rules for | |||
*Booking Conditions | *Booking Conditions | ||
| Line 100: | Line 109: | ||
*Info Codes | *Info Codes | ||
**Exclude Booking Info code = BOOKINGVIRTCARD, EXPEDIACOLLECT, AGODACOLLECT | **Exclude Booking Info code = BOOKINGVIRTCARD, EXPEDIACOLLECT, AGODACOLLECT | ||
<span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} </span> If you receive virtual credit cards from the channels, then enter the Booking Info codes to prevent additional pending payments being added to bookings. | |||
Booking tab: Optional | Booking tab: Optional | ||
*Flag Text = Security Deposit Pending Payment (for example) | *Flag Text = Security Deposit Pending Payment (for example) | ||
*Flag Colour = select the colour as this will be visible in the Calendar/Bookings list | *Flag Colour = select the colour as this will be visible in the Calendar/Bookings list | ||
Booking Info tab: If you do not require an auto action to send a payment link to the guest for payment/authorisation, then this is optional. | Booking Info tab: If you do not require an auto action to send a payment link to the guest for payment/authorisation, then this is optional. | ||
| Line 112: | Line 120: | ||
*Booking Info Text - Refundable Security Deposit pending payment | *Booking Info Text - Refundable Security Deposit pending payment | ||
Invoice tab: | Invoice tab: | ||
*Add a Pending Payment to the booking | *Add a Pending Payment to the booking | ||
| Line 123: | Line 130: | ||
**Payment time = set the time to collect payment | **Payment time = set the time to collect payment | ||
**Invoicee = If you use the "invoicee" function you can select which invoicee the pending payment will be assigned to. | **Invoicee = If you use the "invoicee" function you can select which invoicee the pending payment will be assigned to. | ||
<span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} </span> If you accept Virtual Credit Cards from the channels, then you will need to send a payment link to either collect the guest credit card to then authorise the Security Deposit on their personnel card OR send a payment link so the guest can authorise the payment on their own credit card, it is not possible to take a Security deposit from a virtual card. | |||
'''Auto Action 2 - Send Payment Request with link for Security Deposit Authorisation''' | |||
Can be used for channel bookings with virtual cards or properties/guests in EU countries and required to comply with EU 3DSecure regulations. | Can be used for channel bookings with virtual cards or properties/guests in EU countries and required to comply with EU 3DSecure regulations. | ||
Trigger tab: | Trigger tab: | ||
| Line 146: | Line 145: | ||
*Booking Source | *Booking Source | ||
**Booking Source = | **Booking Source =All (this will apply to all bookings, direct, manual and channels). If you want to have different auto actions/rules for direct bookings -v- channel bookings, then select ‘Direct’ this will include manually created bookings and booking page bookings. | ||
*Booking Conditions | *Booking Conditions | ||
| Line 210: | Line 208: | ||
Booking Info tab: Optional, for information and reporting | Booking Info tab: Optional, for information and reporting | ||
*Booking Info Code = PAYREQ (for example enter the value - use one word only) | *Booking Info Code = PAYREQ (for example enter the value - use one word only) | ||
*Booking Info Text = Enter the description/text to show in for the Booking Info Code. | *Booking Info Text = Enter the description/text to show in for the Booking Info Code. | ||
</div></div> | |||
=Credit Card details at Stripe= | |||
The card will be saved as a new customer in Stripe with the booking number as a reference. Once the new customer is created in Stripe the card can be charged. | |||
Multiple cards can be sent for each Stripe customer and a specific one selected when charging. | |||
Stripe will only accept valid cards. If Stripe reject the card, it's details will still be visible at Beds24. | |||
Info Codes in the "Info" tab of the booking show you which action was performed. | |||
{| class="wikitable" | |||
! scope="col"| Code | |||
! scope="col"| Use | |||
|- | |||
|CARDTOSTRIPE | |||
| card details were sent to Stripe | |||
|- | |||
|STRIPEPAYMENT | |||
| payment imported from Stripe | |||
|- | |||
|STRIPEFAIL | |||
| card could not be sent to Stripe | |||
|- | |||
|CARDEXPIRES | |||
| added when the card expires before check-in | |||
|- | |||
|STRIPEAUTHORIZE | |||
| payment has been authorised by Stripe | |||
|- | |||
|STRIPEREFUND | |||
| refund has been processed at Stripe | |||
|- | |||
|CARDFAILSTRIPE | |||
| card has failed at Stripe, see the note for reason | |||
|- | |||
|} | |||