Bridge is updating the KYC/KYB information you are required to collect from EEA customers during onboarding starting June 15th. Please review this link to start preparing for these changes now if you are using or plan to use the Customer API with reliance.
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. See full Minimal Code Samples below for full sample requests.endorsementsshould includereliancein place ofbase, in addition to any other endorsements that you might include. For example, if your standard endorsements list includes["base", "pix", "spei", "sepa"], then your endorsements list under the reliance model would include["reliance", "pix", "spei", "sepa"].- if
verified_database_atorverified_govid_atis provided, requirements foridentifying_informationare 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_atis 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, Wallets, and other Bridge features
Despite our reliance model, our bank partner maintains strict requirements before they can open a virtual account on behalf of your end customers. Bridge maintains similar requirements for before users can receive access to Bridge Wallets. In addition to the endorsements in your request, Bridge will also add a new endorsement,kyc_reliance_data_received, which must have a status of approved before proceeding.
Example completed webhook
Specific Field Requirements
- Individual Requirements
- Business Requirements
- Associated Person Requirements