.png)
.png)
There are two routes: our API for merchants who want to build the split experience into their own checkout, and our hosted checkout for a faster path with no front-end build. Both can be tested end to end in our sandbox before go-live.
No. Hands In connects to your existing acquirers, gateways and orchestration platforms rather than replacing them. Funds continue to flow through your own PSP relationships and settle as they do today.
Hands In is a payments layer that sits on top of your existing setup and lets a single transaction be paid by more than one person or more than one card. You keep your current PSPs, MIDs and routing rules; we orchestrate the split, the authorisations and the capture on top of them.
We can automatically stop a split payment if your fraud provider flags the transaction as fraudulent. You choose the threshold (for example, 1 or 2 fraudulent card payments within the split).
If that threshold is met, we immediately block the remaining cards in the split and void the rest of the transaction. This prevents spikes in fraud by ensuring that once fraud is detected, no further payments in the same split are processed.
We can also integrate with your existing fraud provider to receive the fraud signals (e.g., flagged cards/transactions) that trigger this behaviour.
Only the declined transaction fails. The customer is shown an error at checkout and can retry that portion with a different card or payment method, while the rest of the split is unaffected.
We facilitate full or partial refunds for both single and multiple cards.
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.
The merchant can configure how many payment methods a customer can split across. We allow you to set a minimum & maximum value to control the number of split transactions the customer can make.
Only if their share changes. If the outstanding amount is covered without altering what each person owes, existing authorisations are untouched and those members don't need to do anything. If the split is recalculated and shares do change, the original authorisations are voided and Hands In emails the affected members to return to the checkout and re-authorise their new amount
The group has a few options. Another member can cover the outstanding share, the person can be replaced with someone else, or the merchant can choose to accept the partially paid booking and handle the remaining amount separately.
No account is needed to take part in a payment using Hands In. When someone joins a group payment, a unique link is generated so they can revisit their payment dashboard as themselves. The only prerequisite is an email address, provided when first joining or creating a group payment, so they can be uniquely identified and emailed updates and receipts.
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.
Yes, within the webhook notification, you could share with us from your acquirers' data of transaction values of above a certain amount, for example, in excess of $500, for which this solution can be presented. The benefit of working with HandsIn is that we can A/B test this with you alongside our launch of our other services
No, it isn't a mandatory requirement, but it is a quicker path to integration. It means Hands In can control the popup shown to customers without you having to further develop your own integration and your checkout around this solution.
When an NSF (insufficient funds) decline is detected, the merchant can display a dedicated recovery page triggered by a webhook notification from the acquirer as part of the Hands In integration. This page presents the customer with a split payment option, allowing them to use multiple cards to complete the transaction and recover a payment that would otherwise have been lost.
Yes. Merchants can connect multiple gateways and keep their existing routing logic, which is useful where different currencies or regions are processed through different providers.
Each split produces multiple underlying transactions mapped to a single Hands In payment record. Both the merchant dashboard and the API expose the parent payment alongside every child transaction and its gateway reference, so reconciliation stays one-to-one against your PSP reporting.
No. Hands In orchestrates authorisation and capture through your PSP; funds move and settle through your existing acquiring relationships, and the merchant of record is unchanged.
We recommend that merchants create a Hands In account and connect you as their PSP. This allows them to keep their existing payment setup and routing rules unchanged.
Hands In can connect to acquirers, payment gateways, and orchestration platforms/APMs.
Hands In is compatible with NDC when it is connected through a hosted payment page for the airline with easy creation of payment links to support NDC flows.
A single PNR is created for passenger groups of 1–9, displayed as one PNR with multiple transactions.
Hands In is compatible with all direct channel payments, including both mobile and web applications
Yes. Hands In can work with your existing fraud setup, including third-party providers such as Riskified and Accertify, as well as in-house fraud solutions. You simply tell us how fraud is currently handled, and we’ll implement the appropriate connection into your payment flow.
You control this, and the limit depends on how your auth and/or capture process is. Instant capture has no maximum, so the checkout can stay open indefinitely. Delayed capture is capped at 7 days (168 hours), since that's how long an authorization can be held before it expires.
There's no minimum, but we recommend allowing enough time for the whole group to join and pay their share
The group has a few options. Another member can cover the outstanding share, the person can be replaced with someone else, or the merchant can choose to accept the partially paid booking and handle the remaining amount separately.
Tour operators, coach and rail operators, accommodation providers, activity and experience sellers, and travel agents. Anywhere a booking is made by a group but paid by individuals, or where a single traveller wants to spread a large total basket across several payment methods.
Yes. Our hosted checkout supports your logo and branding, and merchants building against the API keep their own front end entirely.
Yes. An agent can create a payment link on the fly from our merchant dashboard and send it out by URL, email, SMS or QR code. They can set a fixed amount, by item, split equally across the party, or let each traveller choose their own amount, and they only need the total plus the lead booker's name and email to get started.
Yes. Alongside card splits we support alternative payment methods where your PSP offers them, including PayPal and BNPL options such as Afterpay, Klarna and more.
You control this, and the limit depends on how your auth and/or capture process is. Instant capture has no maximum, so the checkout can stay open indefinitely. Delayed capture is capped at 7 days (168 hours), since that's how long an authorization can be held before it expires.
There's no minimum, but we recommend allowing enough time for the whole group to join and pay their share
Tour operators, coach and rail operators, accommodation providers, activity and experience sellers, and travel agents. Anywhere a booking is made by a group but paid by individuals, or where a single traveller wants to spread a large total basket across several payment methods.
The group has a few options. Another member can cover the outstanding share, the person can be replaced with someone else, or the merchant can choose to accept the partially paid booking and handle the remaining amount separately.
Yes. Our hosted checkout supports your logo and branding, and merchants building against the API keep their own front end entirely.
Yes. Alongside card splits we support alternative payment methods where your PSP offers them, including PayPal and BNPL options such as Afterpay, Klarna and more.
You control this, and the limit depends on how your auth and/or capture process is. Instant capture has no maximum, so the checkout can stay open indefinitely. Delayed capture is capped at 7 days (168 hours), since that's how long an authorization can be held before it expires.
There's no minimum, but we recommend allowing enough time for the whole group to join and pay their share
Yes. Our hosted checkout supports your logo and branding, and merchants building against the API keep their own front end entirely.
Any authorisations taken are released and nothing is captured, so no traveller is charged for an incomplete booking. Alternatively, you can capture what had been authorised up until that point and settle the remaining unpaid balance at a later point.
Yes. An agent can create a payment link on the fly from our merchant dashboard and send it out by URL, email, SMS or QR code. They can set a fixed amount, by item, split equally across the party, or let each traveller choose their own amount, and they only need the total plus the lead booker's name and email to get started.
Yes. Alongside card splits we support alternative payment methods where your PSP offers them, including PayPal and BNPL options such as Afterpay, Klarna and more.
You control this, and the limit depends on how your auth and/or capture process is. Instant capture has no maximum, so the checkout can stay open indefinitely. Delayed capture is capped at 7 days (168 hours), since that's how long an authorization can be held before it expires.
There's no minimum, but we recommend allowing enough time for the whole group to join and pay their share
Yes, we are able to support dynamic fluctuating price changes during the entire checkout time window for a booking.
Yes. Our hosted checkout supports your logo and branding, and merchants building against the API keep their own front end entirely.
Any authorisations taken are released and nothing is captured, so no traveller is charged for an incomplete booking. Alternatively, you can capture what had been authorised up until that point and settle the remaining unpaid balance at a later point.
Yes. An agent can create a payment link on the fly from our merchant dashboard and send it out by URL, email, SMS or QR code. They can set a fixed amount, by item, split equally across the party, or let each traveller choose their own amount, and they only need the total plus the lead booker's name and email to get started.
Yes. Alongside card splits we support alternative payment methods where your PSP offers them, including PayPal and BNPL options such as Afterpay, Klarna and more.
You control this, and the limit depends on how your auth and/or capture process is. Instant capture has no maximum, so the checkout can stay open indefinitely. Delayed capture is capped at 7 days (168 hours), since that's how long an authorization can be held before it expires.
There's no minimum, but we recommend allowing enough time for the whole group to join and pay their share
Yes. Our hosted checkout supports your logo and branding, and merchants building against the API keep their own front end entirely.
Any authorisations taken are released and nothing is captured, so no traveller is charged for an incomplete booking. Alternatively, you can capture what had been authorised up until that point and settle the remaining unpaid balance at a later point.
Yes. An agent can create a payment link on the fly from our merchant dashboard and send it out by URL, email, SMS or QR code. They can set a fixed amount, by item, split equally across the party, or let each traveller choose their own amount, and they only need the total plus the lead booker's name and email to get started.
Yes. Alongside card splits we support alternative payment methods where your PSP offers them, including PayPal and BNPL options such as Afterpay, Klarna and more.
You control this, and the limit depends on how your auth and/or capture process is. Instant capture has no maximum, so the checkout can stay open indefinitely. Delayed capture is capped at 7 days (168 hours), since that's how long an authorization can be held before it expires.
There's no minimum, but we recommend allowing enough time for the whole group to join and pay their share
.png)