🚧PSP integration (e-financing only)

How to integrate e-financing solutions via your PSP

New feature coming soon. Contact us if interested

Description

This mode is only available to integrate e-financing solutions.

A new possibility for e-financing solutions integration is available when as a merchant you are already integrated through a payment gateway of a .

If it is your case, you can easily integrate e-financing solutions as another payment means in the list provided by the PSP.

The list of PSP available is under construction and will be communicated soon.

Step-by-step integration

1. On boarding

During your merchant on boarding, inform your sales support team you want a "PSP integration mode" for e-financing solutions and provide your "" to be registered by RMS back-ends.

If you don't know your "Client PSP reference code" please contact your PSP.

2. Activation of e-financing solutions

Once the "RMS contract" is signed, activation tasks will be operated directly with your PSP. You will have nothing to do with us but your PSP will contact you to test integration results.

Please pay attention that this choice of integration of e-financing solutions has some consequences on the way of using related events webhooks. Because it will be your PSP that will integrate and receive events instead of you as a merchant.

And that's all !!! 🎉

Technical requirements for PSPs

API Integration

As a PSP, you will have to use the same API endpoints as a merchant but you will receive a dedicated API key that will allow you to call API endpoints on behalf of merchants.

As a PSP you will receive one API key for all your merchants. This will avoid integrating API keys each time you onboard a new merchant and during API calls.

Documentation of API is the same except you will have to provide one additional information as a header of the requests

API Reference

Header to be provide: X-BAAS-CLIENT-REF-FOR-PROXI-ID

Sample of API request

curl --location 'https://api.scalexpert.uatc.societegenerale.com/baas/uatc/e-financing/api/v1/eligible-solutions?financedAmount=500&buyerBillingCountry=FR' \
--header 'X-BAAS-CLIENT-REF-FOR-PROXI-ID: {REPLACE BY PSP MERCHANT REFEFRENCE CODE}' \
--header 'Authorization: Bearer eyJlbmMiOiJBMjU2Q0JDLUhT...uOd2XOFU5XizYWQQOKYWZ7XFRlTVPiDO0n6n7js.ok0LOHchQ-geaqy_DenjtgxNnp2jzZEGJMzXBcNdu40'

As explained before, as a PSP you will have to provide the Merchant's reference code for each API call. Thus RMS back-end will recognize it as registered during the "on boarding" by the merchant.

Webhook integration

If you want to receive events through webhook endpoints, you will have to integrate only once independently of merchants integrations. You will receive all your PSP merchants events with additional header X-BAAS-CLIENT-REF-FOR-PROXI-ID allowing you to dispatch them by merchant.

How to subscribe, use Webhooks