Skip to main content
Universal KYB lets you bring business verification you have already completed. You submit the company pack and supporting documents, and Reap reviews them and returns a decision. Use this when your project is configured for Universal KYB. This is one of Reap’s company verification methods. See the KYB overview for the shared company statuses. Managed KYB (hosted session) is unchanged: send redirectUri to Advance company application and use sessionUrl.

How it works

  1. Create a company.
  2. Submit the Universal KYB pack on Advance company application with method: UNIVERSAL_KYB. The first call creates the application. Later calls with the same method amend it.
  3. Upload each outstanding document from nextAction. Company documents use Upload application documents. Beneficial-owner identity documents use Upload related person documents.
  4. When nextAction.type is SUBMIT, call Submit company application. The company moves to IN_REVIEW.
  5. Reap reviews the application and sends COMPANY_STATUS_UPDATED.
Submit is explicit. Uploading the last required document does not lock the application, so you can still add optional documents such as REGISTER_OF_DIRECTORS and BUSINESS_REGISTRY.

Pack

Send method: UNIVERSAL_KYB plus the verified business data. Countries in the pack use ISO 3166-1 alpha-3 codes and dates use YYYY-MM-DD. See Advance company application for the exact fields and limits. Required:
  • Company identity: legal business name, legal form, and business registration number.
  • Addresses: the registered address and the principal place of business.
  • Line of business: the code that best describes what the company does.
  • Email domains: between 1 and 10 domains the company’s staff use for email.
  • Beneficial owners: at least one. For each owner, send your own identifier for them, their ownership percentage, their name, date of birth and nationality, their residential address, and between 1 and 3 identity documents (type, number and issuing country).
Optional:
  • Date of incorporation and business website.
  • ddq (due diligence questionnaire): card authorities (name and role), the expected spend profile, and the number of employees.
  • edd (enhanced due diligence): written source-of-funds and source-of-wealth declarations. Back them with the SOURCE_OF_FUNDS and SOURCE_OF_WEALTH documents below.
Declared ownership may sum to less than 100. A sum above 100 is rejected. If your project issues cards to corporate employees, the email domains Reap validates from the ones you declare decide which employees can be issued cards under the company. nextAction lists what is still required:
  • DOCUMENT_UPLOAD with the outstanding company documents and any outstanding UBO_IDENTITY items (relatedPersonId + uboDocumentType)
  • SUBMIT when required uploads are complete
  • null after submit, or for Managed KYB

Documents

Upload one document type per request.

Company documents

Accepted formats: JPEG, PNG, GIF, PDF, Word (DOC, DOCX), Excel (XLS, XLSX), and CSV. Maximum 5 files per request and 5 MB total. Send a multi-page document as one PDF or as several files in the same request.

Beneficial-owner documents

Each beneficial owner needs a file for every identity document you declared for them in the pack. Reap accepts these identity documents:
  • PASSPORT: the photo page.
  • ID_CARD: a government-issued national identity card, front and back.
  • DRIVERS_LICENCE: a government-issued driver’s licence, front and back.
Accepted formats: JPEG, PNG, and PDF only. Maximum 2 files per request (front, then back) and 5 MB total. The number, type and issuing country you declare in the pack must match the document you upload.

Incomplete submissions

If you submit before every required document is uploaded, the API returns 400 with code: COMPANY_APPLICATION_INCOMPLETE, plus missing and invalid, so you can fix every gap in one pass. When the outstanding items are documents, documents lists each one in the same shape as nextAction.documents, including relatedPersonId and uboDocumentType for beneficial-owner documents.

Review

Reap’s compliance team reviews every submitted application. Reap does not approve a company automatically and ask for documents later: the company stays IN_REVIEW until the review ends, and moves to one of these statuses:
  • ACTIVE: Reap approved the company. The review also decides whether you can issue cards to the company’s employees and which of the declared email domains Reap validated. See Corporate Employees.
  • ACTION_REQUIRED: Reap needs more information. Reap sends the request to you as the program, not to your customer. Your account manager tells you what is needed, you collect it from your customer, and the review continues once Reap has it.
  • REJECTED: Reap declined the company. Contact your account manager.
Until the company is ACTIVE, it cannot hold accounts or issue cards, and you cannot create employee users under it. Reap sends COMPANY_STATUS_UPDATED on each status change.

Testing in sandbox

Simulation runs the same completeness check and sends the same COMPANY_STATUS_UPDATED webhook as a real review.
  1. Submit a complete application as described in How it works.
  2. Call Simulate company status with ACTIVE, REJECTED, ACTION_REQUIRED, or CANCELLED.
  3. Wait for COMPANY_STATUS_UPDATED. The simulate call returns 204 and the new status arrives with the webhook.
Simulating before submit returns SIMULATION_INVALID_STATE. IN_REVIEW cannot be simulated because submit produces it. ACTIVE does not need applicationDetails. Reap uses the submitted application.

Managed KYB

Projects configured for Managed KYB keep the existing flow. Send only redirectUri (or method: MANAGED_KYB with redirectUri). The response still includes sessionUrl. nextAction is null. Get and list application stay the same resource shape.