KYC & KYB

Know Your Customer (KYC) and Know Your Business (KYB) verification is mandatory for users who send funds through the PayItFast platform. PayItFast uses a tiered verification system with transaction limits that vary by jurisdiction. Verification is powered by Sumsub under the hood.

KYC Overview

Verification Levels

PayItFast uses a tiered KYC system. Each level unlocks progressively higher transaction limits.

KYC Statuses

Endpoints Overview

KYC Endpoints

KYB Endpoints

Submit Standard KYC (Level 1)

Initiate the Standard KYC verification flow for an individual user. This returns a redirect URL that opens the PayItFast KYC widget (powered by Sumsub), where the user completes country selection, document upload, liveness verification, and review.

Request Body

Request Example

POST /v2/kyc/standard
Content-Type: application/json
Authorization: Basic <base64(username:password)>

{
  "email": "john@example.com",
  "redirectUrl": "https://www.yourapp.com/kyc-complete",
  "firstName": "John",
  "lastName": "Doe",
  "country": "US"
}

Response

{
  "redirectUrl": "https://pay-widget.payitfast.com/user/initiate-kyc?token=TOKEN",
  "userId": "UX-1231231253213"
}

Response Fields

Submit Advanced KYC (Level 2)

Initiate the Advanced (Enhanced) KYC verification flow for a user who has already passed Level 1. This is required when the user exceeds standard transaction limits. The user will be asked to provide proof of source of funds and address proof.

Request Body

Request Example

POST /v2/kyc/advanced
Content-Type: application/json
Authorization: Basic <base64(username:password)>

{
  "email": "john@example.com",
  "redirectUrl": "https://www.yourapp.com/kyc-advanced-complete"
}

Response

{
  "redirectUrl": "https://pay-widget.payitfast.com/user/initiate-advanced-kyc?token=TOKEN",
  "userId": "UX-1231231253213"
}

Share KYC via Sumsub Token

For organizations with a tripartite Sumsub agreement. Transfers existing KYC data from your Sumsub account to PayItFast via a share token, allowing users to skip the verification widget entirely.

Request Body

curl --request POST \
  'https://api.sumsub.com/resources/accessTokens/-/shareToken?applicantId={{sumsubApplicantId}}&forClientId=payitfast.com_123'

Request Example

POST /v2/kyc/share/same-vendor
Content-Type: application/json
Authorization: Basic <base64(username:password)>

{
  "email": "john@doe.com",
  "name": "John Doe",
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}

Response

{
  "email": "john@doe.com",
  "status": "kyc_success",
  "userId": "UX-1201923942",
  "userName": "John Doe"
}

Error Responses

Share KYC from Third-Party Provider

For partners using a non-Sumsub KYC provider. Submit identity documents directly via a multipart form upload. The documents will be reviewed by the compliance team.

Request Body (multipart/form-data)

Request Example

curl -X POST https://sandbox-api.payitfast.com/v2/kyc/share/third-vendor \
  -H "Authorization: Basic <base64(username:password)>" \
  -F "email=john@example.com" \
  -F "userId=UX-241125161812424" \
  -F "firstName=John" \
  -F "lastName=Doe" \
  -F "gender=male" \
  -F "dob=1990-05-15" \
  -F "phoneNo=+12125551234" \
  -F "country=US" \
  -F "nationality=US" \
  -F "street=123 Main St" \
  -F "city=Springfield" \
  -F "state=IL" \
  -F "postalCode=62701" \
  -F "idDocType=passport" \
  -F "idDocFrontSide=@/path/to/passport-front.jpg" \
  -F "idDocBackSide=@/path/to/passport-back.jpg" \
  -F "idDocIssuerCountry=US" \
  -F "idDocExpiryDate=2030-12-31" \
  -F "idDocUserName=John Doe" \
  -F "selfie=@/path/to/selfie.jpg"

Response

{
  "status": "kyc_pending"
}

Add Additional Documents

Submit additional supporting documents for a user whose transaction volume has reached a threshold requiring enhanced documentation, or when the compliance team has requested supplementary evidence.

Request Body (multipart/form-data)

Request Example

curl -X POST https://sandbox-api.payitfast.com/v2/kyc/share/add-docs \
  -H "Authorization: Basic <base64(username:password)>" \
  -F "email=john@example.com" \
  -F "additionalDocType=bank_statement" \
  -F "additionalDoc=@/path/to/bank_statement.pdf"

Get KYC Status

Retrieve the current KYC verification status for an individual user. If the KYC was rejected, the response includes rejectLabels describing the reasons.

Query Parameters

Request Example

GET /v2/kyc/user?email=john@example.com
Authorization: Basic <base64(username:password)>

Response

{
  "status": "kyc_success",
  "rejectLabels": []
}

Response Fields

Submit Standard KYB (Level 1)

Initiate the Standard KYB verification for a business user. Basic KYB must be approved before Standard KYB can be submitted. The response contains a verification link that expires in 12 hours.

Request Body

Request Example

POST /v2/kyb/standard
Content-Type: application/json
Authorization: Basic <base64(username:password)>

{
  "email": "finance@acmecorp.com"
}

Response

{
  "link": "https://verify.payitfast.com/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9",
  "expiresIn": "12h"
}

Response Fields

Error Responses

Submit Advanced KYB (Level 2)

Initiate the Advanced KYB verification for a business user. Standard KYB must be approved before Advanced KYB can be submitted. Uses the same request and response structure as Standard KYB.

Request Body

Request Example

POST /v2/kyb/advanced
Content-Type: application/json
Authorization: Basic <base64(username:password)>

{
  "email": "finance@acmecorp.com"
}

Response

{
  "link": "https://verify.payitfast.com/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9",
  "expiresIn": "12h"
}

Error Responses

Get KYB Status

Retrieve the current KYB verification status for a business user.

Query Parameters

Request Example

GET /v2/kyb/user?email=finance@acmecorp.com
Authorization: Basic <base64(username:password)>

Response

{
  "status": "user_approved",
  "rejectLabels": []
}

KYB Status Values

Reject Labels

When a KYC submission is rejected, the rejectLabels array in the status response contains one or more of the following codes explaining the reason for rejection.

Document Issues

Identity Verification

Data Inconsistencies

Fraud & Compliance

Administrative

Supported ID Documents

The following identity document types are accepted for KYC verification.

Next Steps

After completing KYC or KYB verification, users can begin transacting on the platform: