We do not handle any of your systems inventory. Our system creates an order based on the products being paid for. Once the transaction has completed, you will be notified and how you handle this in your system is up to you.

When a single or group payment is created you can store a reference ID within it (take a look at docs), to help reconcile with an internal reference order.

Hands In supports multiple refund flows, both through the Merchant Dashboard and API. In particular we support: Full group payment refunds Single customer refunds Partial customer refunds Otherwise, if you would like to make refunds outside of our platform, these can be done through finding and refunding payments through your connected PSP's dashboard as described here.

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. If you are struggling to find the reference to a payment on your PSP check out our docs for looking up a group payment here https://docs.handsin.co.uk/docs/how-to-find-a-group-payment-in-my-psp-dashboard

All of our custom built packages provide a completely white-labelled service. Our Pay As You Go plan will not offer white-label services. If you would like to receive a white-labelled version of our products, please get in contact with our sales team at sales@handsin.com

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 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

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.

No, this is a card-based solution only. If you're interested in us offering other alternative forms of payment, please contact us at contact@handsin.com.

This constitutes a single payment with multiple transactions, which can be reconciled either within our system or through our API.

We do not handle any of your systems inventory. Our system creates an order based on the products being paid for. Once the transaction has completed, your system will be notified though webhooks and how you handle this in your system is up to you.

Our system supports instant and delayed capture. The current maximum length of time we support for a payment authorisation can be is 7 days (168 hours). For delayed capture payments 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.

Our system is similar to how hotel payments are captured at check-in where a buyer typically has their card pre-authorized by the hotel upon checking in and then upon checking out the payment amount is then captured and the card is then settled. We do the exact same, upon each user agreeing to pay we pre-authorize the payment and freeze the funds in their bank account, once the total payment amount has been made up by the group the funds are captured from each users bank account and the cards are settled.

If a group size changes and the total authorization amount per person changes, the original authorization amounts are cancelled and paid-up group members are required to re-authorize a new payment share. Card details are automatically saved at the checkout. So now when a group member cancels or defaults from payment and the remaining group members are required to reauthorize a new payment share an email is sent from Hands In to head back to the checkout and reauthorize the new payment amount. Completing and capturing the payment in seconds despite the drop off from one group member.

Retailers and customers and provided a number of 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) Pay on behalf: Any other group member can pay on behalf of the unpaid participant. Meaning any group member can pay for somebody else that has not paid yet. C) Merchant does partial payment: We also support partial payments, so if a Merchant would still like to capture money from a group even though the total amount was not made up, they can. However, If a Merchant does NOT accept partial payments and someone has NOT paid into the group by the expiration date then we will void all the payments made into a group, returning all money back to the group members.

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.

At most 30. We recommend trying to keep the group size within 2 - 30 people. If you require bigger size groups please get in contact with us and we should be able to accommodate your request.

Yes, all of our solutions are completely white-labelled. Please get into contact with a member of our team or reach out to us via contact@handsin.com to learn more!

Each payment made into a group has a reference ID that is unique to the group payment. This information is stored in the group payment record. You are able to handle reconciliation by either searching for this ID within your connected PSPs or more easily, through our API you can fetch all the payment records made into a group payment.

Yes you can pay on behalf of another member.

Only the lead booker of the group is able to remove a member. The member must also not have made a payment.

You can refund customers via our Merchant Dashboard or API. We support both partial and full refunds at both the group and customer level enabling you to handle every refund scenario.

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 can support dynamic pricing, if required at the checkout by pre- authorising a slightly higher amount (with end-user approval) than the actual checkout.

This is set by the merchant business that is using our multi card solution via the Merchant API. Merchants can set a hard limit of the number of cards a multi card payment can consist of. If the merchant does not set a limit, then there is no restriction on the number of cards that can be used for a multi card payment.

Multi Card payments work by rendering a web widget. This can be embedded onto any page on your website and is available using our JS SDK library for embeddable widgets.

We support SCA and 3DS authentication flows on each card payment. This means that once a customer clicks pay for each card payment, we will perform necessary checks to ensure the card is not fraudulent and if necessary display their banks verification screen where they can authenticate each payment.

The minimum amount can vary depending on the payment gateway you use as well as the currency. Generally, the minimum is the equivalent to £1, however we recommend you double check this with your payment service provider/gateway.

Typically this will usually include card brands such as Visa, Mastercard, American Express, however we accept all cards that are accepted by the payment service provider/gateway that you connect to Hands In.

We support issuing full or partial refunds to a single and multiple transactions. For example if you would like to issue a refund for the entire transaction purchase you can start a refund on the entire multi-card purchase. Otherwise if you would only like to refund a single card, you can select this via our dashboard and issue a single refund on one of the cards. Chargebacks are not handled by Hands In. We can provide you with all the necessary information on each payment to help you handle any chargebacks that arise, but this will be primarily dealt between you and your acquirer

No, given we’re integrated into your existing gateway and acquiring infrastructure, we can operate in the same regions your PSPs can operate in.

No, this is a card-based solution only. If you’d be interested in us opening up other alternative forms of payment please let us know at contact@handsin.com

The customer receives an error message and can attempt the payment again with another card.

Our system supports instant and delayed capture. Currently the maximum length of time a group payment can be is 7 days (168 hours). There is no minimum but we recommend a suitable enough of time to give everyone in the group enough time to join and pay. This can be tested via our sandbox.

Yes you can via our merchant dashboard.

Your customers have several ways to split a group payment when using Hands In. Currently, we support three main ways: equal, by item & fixed price. Equal split allows each member of the group to pay the same equal portion of the total amount, making it easy to split the payment evenly across the group. Split by item allows each member of the group to pay for the specific items they have been assigned. This can be useful when certain members of the group want to pay for specific items in the group payment's order that may cost more or less than what others want to pay for. Fixed price allows each member of the group to pay the same specific fixed amount. This can be perfect for groups that are buying products such as tickets, which all cost the same amount. In addition to these options, we are constantly working on adding more ways for your customers to split payments. Options include: Splitting by custom amounts, which would allow each member of the group to pay a custom amount/share of the total. Splitting across multiple cards, which would allow an individual to split the total cost of a payment across multiple cards. Payment installations also known as Buy Now Pay Later, which allows an individual to pay a total amount across an extended period of time such as 3 months If theres any options we have or have not mentioned here that you are interested in specifically, please feel free to reach out to us as we are happy to discuss them in further detail with you.

Payment reminders are an essential part of ensuring that group payments are made on time and that everyone pays their fair share. 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. The frequency and number of reminders that we send out depend on the length of the checkout period. For group payments that last between 4-7 days, we send out four reminders to all group members, including at least two reminders to the merchant and lead buyer of the group as an overview of the group's payment status. For group payments that last between 2-4 days, we send out three reminders to all group members, including 1-2 reminders to the merchant and lead buyer of the group as an overview of the group's payment status. For group payments that last between 2 hours and 2 days, we send out one-two reminders to all group members, including one reminder to the merchant and lead buyer of the group as an overview of the group's payment status. For group payments that last less than 2 hours, we may send out at most one reminder to all group members and the merchant/lead buyer of the group as an overview of the group's payment status. However, for very short-length group payments, it's possible that no scheduled reminders are sent out. This is due to the fact that short lived group payments don't require any reminders as emails would have been sent out as normal to notify this person to join and pay anyway. By sending out automatic payment reminders, we help ensure that group payments are made in a timely manner, reducing the risk the group payment failing. This helps to make the payment process more convenient and efficient for everyone involved.

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 as a merchant as well as the group leader are able to kick them from the group.

Simply use our Merchant dashboard to find, view and refund. You are able to issue both partial and full refunds to the everyone in the group (full entire group refund) or even just a single customer in the group.

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 operate with your current GDS system.

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.

Only a single PNR is created

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 interoperable between booking engines.

Once all the funds have been captured by your payment gateway(s) you can issue a virtual card to pay your supplier.

Yes, we are able to support dynamic fluctuating price changes during the entire checkout time window for a booking.