Payments

Routing

For any of our integrations, our services can act as a fully managed payment service. However, if you already have in-place payment processing solutions, we are also connected to a wide range of payments actors to route your payments to your existing processor.

3D Secure payments

1.0

3D Secure payments (or 3DS 1.0) is a recognized safeguard for merchants and buyers against fraudulent usage of credit cards by adding a second layer of security when completing the payment process. The goal is to securely authentify the credit card holder. After typing his credit card details on the payment page, your customer is displayed his bank 3DS page and is required to confirm that he is the bearer of the card via an authentication method: code sent by text message or requirement to enter the birth date are the most widely used methods.

Transparently integrated within our UXs, the can be configured for your platform.

2.0

3DS 2.0 is designed to help merchants in Europe comply with the new Strong Customer Authentication (SCA) requirements that were introduced by the revised Payment Services Directive (PSD2). Previously driven by merchant's decision to ask for 3DS authentication. The risks are now endorsed by the customer's bank. So it is now up to the bank to request for 3D Secure authentification.

3DS2 is managed by our widget so you don't have to care about complicated multi JS third-party integration (as it is sometimes the case with PSP's).

In case of 3DS2 unavailability, payment fallback to 3DS1 when ever possible.

Depending on your Sharegroop platform payment routing configuration, it may requires more customer information to be shared upon payment request, to avoid 3DS authentification being requested to the customer.

Tokenization

We can avoid your users having to re-enter their bank card number for subsequent payments by tokenizing their payment method. In adequacy with your choosen Sharegroop integration workflow, it allows to transparently enhance your user exerperience.

Refunds

Refunds can be managed at Order or Transaction level, full or partial via Dashboard or API (see our API References).

If you call a partial refund at Order level when multiple transactions are involved, sharegroop transparently manage refunds on each transactions depending on the concerned module logic (so that you only have 1 click or 1 API call to call).

WARNING

As it is usual practice in the payment industry, your platform must have sufficient funds to proceed to refunds. Hence, in full-service model and during your on-boarding, we may require you to provision a cash reserve to support periode of refunds overcoming cash-ins if your transactional volume justifies it.

Getting paid

During your platform configuration by ShareGroop, we set up a withdrawal frequency that will trigger a bank transfer of your cumulated captured order (or confirmed order for pre-funded platform).

If a accounting reconciliation is necessary, withdrawal operations will be listed in our reporting with all related orders operations linked to it.

If the transfer payment does not suit your needs, we also provide a way to pay our Clients via generated eCard for you to process.

If you orchestration model is Gateway Router, we do not trigger withdrawals, and let you manage your withdrawals.

Ask support@sharegroop.com for more informations.