Skip to main content
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.
The Customers API enables you to directly pass the KYC information to Bridge. This endpoint enables you to control the UI independently and handle all of the back and forth with customers, regardless of whether they are individuals or businesses. To determine whether a customer is able to use the platform, Bridge monitors the customer’s kyc_status and the status of each requested endorsement, e.g.base endorsement for access to US rails. If Bridge is able to validate the information, the customer will receive KYC approval and be granted the requested endorsement(s) to use Bridge’s platform. If certain information was invalid or missing, the customer object will return the appropriate KYC status, endorsement status, and endorsement requirements. After obtaining a signed_agreement_id (details here: Terms of Service), you can now use the Customers API to create customers as follows.

Individual customer creation

You can use the following endpoint.
Note: proof_of_address_document may be required for individual customers from European Economic Area (EEA), or customers who wish to use SEPA/Euro services offered by Bridge, if conflicting location signals are detected. Please refer to SEPA/Euro Transactions page for details. For international customers, submit an ISO 3166-1 alpha-3 country code and an ISO 3166-2 subdivision code (minus the country prefix) for the state. So for the above example, GB-MAN is the code, but just MAN is submitted.

Business customer creation

Customer status

Upon customer creation, Bridge will review the submitted customer information and return statuses for both overall KYC (kyc_status) as well as a status for each requested endorsement (e.g. base, the endorsement for US rails, will have its own status). Bridge recommends using both kyc_statusand endorsement status to determine the customer’s ability to use the Bridge platform.

KYC status

Upon customer creation, Bridge will review all KYCs for the customer and return a status field that denotes the KYC status (as applicable) for the user (example KYC statuses include not_started, active, or rejected). The average decision time for KYC is typically less than one minute. If a manual review is required for KYC, the decision may take until next business day. KYB reviews typically happen same business day, up to next business day.
Response
While KYC generally works quickly, there are edge cases that are important to account for. Here are a few examples of how the KYC status of a customer could progress:
  • not_started -> incomplete
    • The customer has submitted a partial application but additional information is still required before they can be considered for onboarding.
  • not_started -> awaiting_ubo
    • Applies to business customers with one or more Ultimate Beneficial Owners (UBOs) who have not yet completed their applications. The customer’s review will remain blocked until all listed UBOs have submitted complete applications.
  • not_started -> active
    • The happy path for individual customers. The submitted information passed all automated checks and the customer was approved within seconds of submission.
  • not_started -> under_review -> active / rejected
    • All business customers, and some individual customers, require manual due diligence before reaching a terminal state. During this phase, the compliance team reviews the customer’s submitted information before issuing a final decision.
  • not_started -> rejected
    • The customer’s submitted information did not pass KYC checks and they are not permitted to transact.
  • deposits_restricted
    • This status can be reached from any other status in the system and indicates that the customer is restricted from making new deposits. Any new deposits made by the customer will be auto-returned. The customer may still transact with or withdraw funds that have already been deposited with Bridge.
  • paused
    • This status can be reached from any other status in the system and indicates that the customer’s account is currently under review for an account-related reason.
  • offboarded
    • This status can be reached from any other status in the system and indicates that the customer’s account has been permanently closed, either following a compliance review or at the request of the customer or developer.
customer_kyx_journey.png

KYC rejection

Sometimes, your customer could immediately move from not_started to rejected and skip under_review entirely. The primary reason this happens is when the tax identification number is entered incorrectly. Without a valid tax identification number, Bridge is unable to verify any of the other details you have submitted for your customer (birth date, address, name, or business details). In this scenario, the customer starts off not_started, but after attempting to verify submitted information, there was an issue detected with the submission. It is possible to move directly to rejected and skip under_review entirely. In the rejected scenario, fetching the customer via Get Customer would result in something like this:
You can see that the customer’s KYC status is rejected and that there are two fields shared with rejection reasons:
  • developer_reason is meant to be used by developers for internal purposes only. This field can contain sensitive information intended for only the developer and is provided to help with troubleshooting potential issues or protecting against potential abuse.
  • reason can be shared by a developer directly with their customers.
For reference, see our page on Rejection Reasons for developer_reason and reason mappings for KYC rejection reasons.

Updating Customers

After the initial submission, customers can update any portion of their application at any time using the update customer endpoint. This endpoint accepts partial request bodies and mirrors the shape of the create customer endpoint, so only the fields being updated need to be included. Note: Rejection does not permanently bar a customer; they can resubmit any portion of their application at anytime and continue through the KYC process.

Supported Government ID’s by Country

Y = Yes (Supported) | * (Requires backside )