What is reliance?
For most developers, Bridge runs thorough verification on all input KYB/KYC data provided for end customers. If a developer has a robust KYC/KYB program for their customer base, Bridge may (after reviewing the developer’s policies/procedures) approve the developer for a reliance arrangement with Bridge. This means that Bridge and the developer agree that the developer will be in charge of verifying KYC/KYB data for end users. With this, there are certain additional data requirements for how Bridge APIs are used. Such an arrangement is beneficial for developer costs as well as in streamlining end customers’ onboarding experience.Additional Fields we Require
This is in addition to the normal requirements for creating a customer- if
verified_database_at
is provided, requirements foridentifying_information
are loosened:- you do not need to include a government ID image
- you still need to include a number from a form of identification, but it can come from any a tax document or a standard ID document type (e.g., unlike in other cases, including a drivers_license with a number would be sufficient)
verified_proof_of_address_at
is required if proof of address would otherwise be required (i.e. customers residing in the EEA or customers who wish to use SEPA rails).
Accessing Virtual Accounts
Despite our reliance model, our bank partner maintains strict requirements before they can open a virtual account on behalf of your end customers. After providing sufficient information to Bridge via API for your customer to unlock virtual accounts, they should (asynchronously) receive thekyc_reliance_data_received
endorsement.