Getting Started with Reap's KYCaaS
This guide introduces the key concepts and terminology used throughout Reap’s KYC-as-a-Service (KYCaaS) platform
Overview
Reap KYC-as-a-Service (KYCaaS) is a identity verification solution designed to help businesses looking to run Card Issuance programs with Reap. Through a simple API integration, businesses can initiate KYC checks, collect documents via the SumSub SDK, and receive verified identities for downstream card issuance.
Key Terminology
Business
The Business refers to you — the organization integrating with Reap’s KYCaaS platform to verify your end-users (e.g. cardholders). Each business is issued a unique API Key and Business UUID (BUUID). All activity (entity creation, verification, result handling) is scoped to your BUUID
Feature
A Feature is a permission or capability that has been enabled for your business. In the case of KYCaaS, the main feature is Card Issuance — the ability to verify individuals for the purpose of issuing payment cards
Requirements
Requirements are the specific pieces of information or documentation that must be collected from your end-user to complete KYC verification. For KYCaaS, this includes: Government-issued ID, address, and liveness check
Entity
An Entity represents the individual end-user you are verifying through KYCaaS. In the current version of KYCaaS, entities are always of type INDIVIDUAL. Each entity is identified by a unique entityId in the system. You can link this to your internal user record via externalId
Updated 4 months ago