We have 2 direct styles of integrations, we also support a range of payment service provider aggregators. For direct integrations, the merchant integrates with Yaspa - the only difference between the 2 options below is how the journey is started.
Hosted journeys
Hosted journeys are the newest and simplest integration. Here, when the payment instruction is submitted from your server, Yaspa will return a URL to you. You can open this URL for the customer in either an iframe or in a new window.
With hosted journeys, merchants do not need to worry about customer devices, mobile or desktop. Yaspa takes care of transitioning the customer to mobile from desktop and keeping journeys in sync. See the API sections here:
SDK journeys
SDK journeys are an older form of integration. They are designed to allow Yaspa to be opened within the same JavaScript sandbox as the merchant’s site without the need of an iframe or new window. For merchants who have very specific requirements, SDK journeys may be a more appropriate solution.
With SDK journeys, merchants can customise the customer experience on mobile or desktop. The merchant can open either QR journeys or email journeys on desktop, and standard journeys on mobile.
At present, only the SDK supports account verification journeys – these journeys provide the verification of the user without making a payment and can be used in KYC, fraud or AML scenarios. See the API sections here:
Payment Service Provider Aggregators
Merchants who already have integrations with PIQ, Praxis or Hexopay will not need to concern themselves with the integrations above. Instead, they will be configuring Yaspa within the respective applications. However, there is still some minimal work required to set up Yaspa with these aggregators.
Related articles
- Taking the Yaspa Integration Questionnaire
- Setting up Postman to make a test payment