Yes, we support all major card types, including AMEX,Visa, MasterCard, JCB, and others, as well as serviceslike Apple Pay and Google Pay, with the ability to addmore as needed.
This constitutes a single payment with multiple transactions, which can be reconciled either within our system or through our API.
We pre-authorize each card when a payer provides us with their card information. Funds are only deducted when the last person or card commits. If one person or card drops out, the payment can still proceed, as all other funds are temporarily placed on hold.
We support both SCA and 3DS on each card payment. This means that once a customer clicks the pay button on each card we will run card verification and if necessary will show them their bank's verification screen.
Please note that chargebacks are not managed by Hands In. We provide comprehensive payment information to assist you in handling any chargebacks directly with your acquirer.
Hands In operates at a layer above payment service providers (PSPs), ensuring full PCI compliance. We do not store any card details within our system, and all card processing is handled by the PSP that you connect to your Hands In Merchant account.
We send out automated payment reminders to everyone in a group via email and SMS. Additionally, all participants can send reminders to others in the transaction. The schedule for automated reminders depends on the length of the booking window.
We manage dynamic pricing at the checkout by authorising a slightly higher amount (with end-user approval) than the actual checkout.
You can refund customers through our Merchant Dashboard or API. We support both partial and full refunds at both the group and customer levels, enabling you to handle every refund scenario.
The booking window is completely customisable and set by the merchant. Hands-In can support checkouts as short as 5 minutes but can also extend up to 7 days.
Retailers and customers are provided with several options.
A - Lead booker removes:
If someone drops out before the expiration date, the lead booker can remove them from payment. Other group members can pay on behalf of the dropout.
B - Lead booker pays on behalf:
We support partial payments, allowing the lead booker or group members to pay on behalf of others.
C - Merchant does partial payment:
If a Merchant doesn't accept partial payments and someone hasn't paid by the expiration date, we void all payments into the group, returning money to group members.
The customer receives an error message and can attempt the payment again with another card.
Multi Card payments work by rendering a web widget. This can be embedded on any page of your website, including the checkout page. Additionally, upon payment decline, it appears as a pop-up, allowing users to retry spreading payments across a series of cards.
We facilitate full or partial refunds for both single and multiple cards.
- For a full purchase refund, initiate it for the entire multi card purchase.
If you prefer refunding a single card, simply select the option and issue the refund.
The minimum amount is $1, and the amounts are set by the payer. We can accept all cards that are accepted by the PSPs you connect to Hands In.
Limited to 4, this could be extended upon request.
No, you can create a group just by entering the amount of money to capture, and adding the name and email of the group leader (also known as the lead booker/organiser).
You can refund customers through our Merchant Dashboard or API. We support both partial and full refunds at both for entire group payment and for each individual transaction, enabling you to handle every refund scenario.
Hands In sends out automatic payment reminders to all the group members who have not yet paid, we send these out on a scheduled basis.
If the checkout period is:
Yes, you can manage a transaction including removing people from a group payment transaction via our merchant dashboard
Your customers have several ways to split a payment when using Hands In:
Group Payment
For groups that want to pay, you can split the total equally, by individual items, custom amounts, or use a fixed-price option where everyone in the group pays the same amount.
Multi Card
For individuals that want to split the total across multiple cards, or to split the total into multiple smaller transactions and pay using the same card multiple times.
Installments
For customers that need more flexibility to split the payment over time
The booking window is completely customisable and set by the merchant. Hands-In can support checkouts as short as 5 minutes but can also extend up to 7 days.
Our system supports both instant and delayed capture payments. The current maximum length of time we support for a booking window can be is 7 days (168 hours). There is no minimum amount of time but we recommend a suitable amount of time to give everyone in the payment enough time to join, pay and complete the payment.This can also be tested via our sandbox.
Yes, we are able to support dynamic fluctuating price changes during the entire checkout time window for a booking.
Yes, simply just set the "autocomplete" field of the payment to false and trigger your fraud analysis tool on the webhook event "PaymentCreated". From here your fraud tool can decide whether to decline or accept the payment.
No, Hands In’s payment connection relies solely on havingaccess to the merchant's hosted payment page, whetherprovided by a partner or directly managed by themerchant.
Hands In is compatible with all direct channel payments, including both mobile and web applications
A single PNR is created for passenger groups of 1–9, displayed as one PNR with multiple transactions.
Yes, we can operate with your current GDS system.
Hands In is compatible with NDC when it is connected through a hosted payment page for the airline