There are a range of add-on services to this product, please see them below:

Payout Approvals

To learn more about Payout approvals please see Payout Approvals

Closed Loop Payouts

This add-on supplements Hosted Payouts. When a Closed loopPayout is made, the customer is presented with only a list of bank accounts they have previously used for pay-ins. The bank selector is not available, and new bank accounts cannot be connected. This AML feature stops customers from paying in from one account and then performing a payout to another account. To use this, send disableAddingNewBanks in the request, see this under the optional fields Here

📘
Direct Payouts can be Openn or Closed Loop
Due to Direct Payouts being managed by the merchant, there are two options:

The merchant can only show previously used payment methods, making a closed loop process across all payment options.

The merchant can allow users to enter bank information and pass that to Yaspa, allowing for a completly open system.

Payouts Allowing Manual Input

This add-on supplements Hosted Payouts and lets customers type in their bank details. Ideal for users unfamiliar with mobile banking. This is especially useful in regions like Germany where manual IBAN entry is common.

📘
Manual entry creates an open-loop payout.

KYC Data

Enabling Feature

Add the customerDetails parameter to the pay-in instruction with a JSON object of additional key/values from the table below.

Description

Customer data can be passed into the Pay-in and Payout instructions. This allows Yaspa to answer EMI Request For Information (RFI) requests for PEPs and Sanctions requests on the merchant's behalf.

Yaspa advises merchants to send us customer details in order to streamline RFI requests from the bank. This allows Yaspa to manage 90% of RFI's without having to contact the Merchant.

Any or all of the following optional data can be passed into the instruction to help with RFIs

Field	Description	Type	Example
`sex`	Sex. One of: `"MALE"`, `"FEMALE"`, `"UNKNOWN"`, `"X"`	string	`"UNKNOWN"`
`firstName`	First name	string	`"John"`
`lastName`	Last name	string	`"Jonsson"`
`street`	Street address	string	`"Epworth 1"`
`city`	City name	string	`"London"`
`state`	State name or ISO 2 (abbreviated when applicable)	string	`"London"`
`zip`	Postal zip code	string	`"EC2A 4DN"`
`country`	Country code of residence (3-letter ISO), e.g. `GBR`, `SWE`	string	`"GBR"`
`email`	User's email	string	`"[email protected]"`
`dob`	Date of birth in format `YYYY-MM-DD`	string	`"1970-01-01"`
`mobile`	Mobile number including country code. Prefixed with `+`, no spaces/delimiters	string	`"+46733123123"`
affiliateId	Where the payment can be attributed to a specific traffic affiliate, the affiliate ID can be passed to Yaspa who can provide insights on the trends around specific groups of traffic.	string	Website101
brandName	When merchants integrate with Yaspa via a PSP, sometimes the original lobby URL is masked. In these cases, Yaspa asks the merchant to pass through the lobby URL here - this aids support and diagnosis of merchant issues	string	Merchant Site NL
customerValue	This string represents the customer value as perceived by the merchant. This will allow Yaspa to generate insights on trends for subcategories of users and also help to increase accuracy for categorisation.	string	VIP 5000

Example:

{ 
   "reference": "ud6i4vcf5dqa",
   "customerIdentifier": "ud6i4vcf5dqa",
   "paymentGiro": "FPS", "amount": "2",
   "currency": "GBP",
   "payload": "payload123",
   "journeyType": "HOSTED\_PAYMENT",
   "customerDetails": {
      "sex": "UNKNOWN",
      "firstName": "John",
      "lastName": "Jonsson",
      "street": "Storgatan 1",
      "city": "Stockholm",
      "state": "Stockholm",
      "zip": "177 32",
      "country": "SWE",
      "email": "[email protected])",
      "dob": "1981-01-01",
      "affiliateId":"Website101",
      "customerValue":"VIP 5000",
      "brandName": "Merchant Site NL",
      "mobile": "+46733123123"
   }
}