How to reduce non-payment risks of your customer ?


A customer, holding a payment card delivered by your institution, carries out an e-commerce transaction with this card. The customer previously granted authorization to your institution.

Through the "Funds Availability" API, provided by the bank, your institution can ask to check if a given amount can be covered by the liquidity that is available on the customer cash account or payment card, minimising the risk of non-payment.

The bank answers with positive or negative response, without setting aside the amount or executing the transaction..

The "Funds Availability" API resources (see the use case "Use and check funds availability") can only be consumed by the PSP having the Card Based Payment Instrument Issuer role, this prerequisite is described in the "Eligibility" section.

One this prerequisite completed, the global process is: 


1- The customer and you have a contract and he owns a card that you issued. This card allow debits on one of the customer's accounts held by his bank. The customer has acces to your application.

2- First of all, before any payment coverage check request, the customer must have forwarded his consent to his bank, giving you access to his account for 90 days.

3- If authorization was granted by the customer, you can ask for an OAUTH2 access token retrieval, using 89C3 platform and according to secured exchanges (see the use case "Retrieve your access token")

4- After providing this access token, which is needed to use our API, you will be able tu reduce you non-payment risks by asking the bank to check if a given payment can be covered or not by the funds available on one given customer account for a 90 days period, before asking the customer to process again the strong authentication every 90 days in order to renew your access to his accounts.

The full process description explaining how to consume Funds Availability API is visible in the use case "CBPII Process".