Yaspa supports three broad categories of payment verification and these affect the way payments are made.
Verified pay-ins
In open banking parlance, a verified pay-in is an AIS (account information service) request followed by a PIS (payment initiation service) request. The AIS request allows Yaspa to access details of the customer, such as their name and account details. There are two main reasons to make a verified pay-in:
- The customer’s bank is in a country where account information is needed to make a PIS call.
- The merchant wants the customer's name or bank details for KYC and verification checks.
Once a verified pay-in has been made, the customer identity is remembered and future payments will be streamlined to the PIS check only.
Unverified pay-ins
In open banking parlance, this is a PIS call. An unverified pay-in is the quickest way to make a payment for the user. This is akin to an anonymous checkout where the customer details are not requested or remembered. The two main reasons to make an unverified pay-in:
- The shortest customer payment experience is required.
- No customer data is needed for verification by either the merchant or the bank for the PIS call.
Enhanced pay-ins (new in January 2024)
Enhanced pay-ins offer the advantages of both verified and unverified pay-ins. The customer payment experience is optimised, whilst still remembering customer details for future payments and returning customised customer details to the merchant for verification purposes.
Enhanced pay-ins offer all the benefits by optimising the payment experience on a per bank basis. Enhanced pay-ins should be used in all cases – save one:
- If the customer details are required at the ACCEPT stage of pay-ins, then only verified pay-ins can obtain this. Enhanced pay-ins only have access to this data when the payment is completed.
If you are unsure which payment verification type to use, please see the Yaspa questionnaire.
Related articles
- Taking the Yaspa integration questionnaire
- Understanding the pay-in journey
- Understanding pay-in webhook notifications