KYC reliance

---

If you have already verified the customer, we can process this KYC data via API request and make additional risk checks on our end during the transaction creation.

To use this feature, the Customer Takeover Data parameters (see above) and additional KYC reliance parameters are mandatory - please see the initiate payment API call for details. The additional parameters relevant to KYC reliance feature need to be sent in the "customer_takeover_data" -> "document" object.

The additional parameters include the document ID, document type, document date of issuance and expiry, document issuing authority and tax ID.

• If the checks on our end fail, we will return the error code 3161 ("action_not_allowed").
• Since the Customer Data Takeover is mandatory for this feature, we will return the error code 3150 ("missing_mandatory_parameter") in case one of the parameters is missing.
• If the KYC data is invalid, we will return the error code 10028 ("invalid_request_parameter")
• If the customer reached their limit, we will return the error code 33005 ("merchant_client_limit_reached")
• If the customer is soft-declined after the risk check, we will return error code 2705 ("soft_risk_decline").
• If the customer is hard-declined after the risk check, we will return error code 2706 ("hard_risk_decline").

Customer data takeover & KYC/KYB Reliance parameters:

Parameter	Required	Data Type & Length	Example
first_name	Mandatory	string - max 80 characters	Max
last_name	Mandatory	string - max 80 characters	Mustermann
date_of_birth	Mandatory	string - max 6 digits (ISO8601 -> YYYY-MM-DD)	1990-12-31
address1	Mandatory	string - max 105 characters	Musterstrasse 2
postcode	Mandatory	string - max 10 characters	1234
city	Mandatory	string - max 80 characters	Vienna
country_iso2	Mandatory	string - max 2 characters (ISO 3166-1 alpha 2)	AT
phone_number	Mandatory	string - max 19 digits	+43676123456789
email	Mandatory	string - max 80 characters	example@test.at
document	Mandatory	Array(object)	-
document: id_number	Mandatory	string - max 80 digits	8010369012345
document: type	Mandatory	string - enum - max 15 characters	Valid values: PASSPORT, ID_CARD, RESIDENCE_CARD, DRIVING_LICENSE
document: issuing_authority	Mandatory if available	string - max 80 characters	Passport Service Paris
document: date_of_issauance	Mandatory if available	string - max 6 digits (ISO8601 -> YYYY-MM-DD)	2010-12-31
document: date_of_expiry	Mandatory	string - max 6 digits (ISO8601 -> YYYY-MM-DD)	2030-12-31
tax_id	Mandatory only in Italy	string - max 40 characters	1NTEST01SGxo9HZ
place_of_birth	Optional	string - max 80 characters	Versaille
kyc_level	Mandatory	string - max 3 characters	FULL
kyc_reliance_type	Mandatory	string - max 21 characters	Valid values: KYC_RELIANCE, OPTIONAL_KYC_RELIANCE, KYB_RELIANCE, KYB_SME_RELIANCE
ip_address	Optional	string - max 45 characters	127.0.0.1
geo_information	Optional	Array(object)	-
geo_information: lat	Optional	string - max 8 characters	48.42111
geo_information: lng	Optional	string - max 8 characters	16.21466
mcc	Mandatory when kyc_reliance_type is set to either KYB_RELIANCE (in case of Sole Trader) or KYB_SME_RELIANCE (in case of KYB SME/Full-fledged)	string - max 4 characters	7995

Geofencing

As part of our KYC Reliance enhancements, we’ve added geofencing for barcode payments. You can restrict redemption to a configurable radius around the barcode’s generation geolocation and within a specified timeframe. An optional webhook can notify you whenever a payment is rejected for violating the radius or timeframe conditions.