Skip to main content
POST
Submit KYC using the same ISO 3166-1 alpha-2 country code stored on the customer profile. All Tier 1 requests also require the customer’s residential address, date of birth, and phone number. Use E.164 phone format, such as +447911123456, outside Nigeria and Ghana. FULL requests include both information and document.
The KYC country must match the country supplied when the customer was created. Supply the customer’s real residential address for identity verification. Card billing-address configuration is separate; do not substitute a default billing address for the residential address.

Asynchronous Card Verification for Non-Nigerians

The non-Nigerian card KYC guide describes the production document-verification flow for DEFAULT USD cards.
Saving KYC here does not start asynchronous card verification or create a card. After saving the required information and documents, request a card to initiate verification. A pending result returns HTTP 409 with CARD_VERIFICATION_PENDING and no card debit. Check card verification status, then submit issuance again after can_create_card becomes true. The existing Nigerian BVN path stays synchronous. Customer KYC tier approval and card-verification approval are separate states.

Correcting Existing Customer Information

Use this endpoint to correct an existing customer’s KYC information, including an approved Tier TWO customer. Submit tier: "ONE" with the complete information object, not just the changed field. Existing Tier TWO and documents are preserved. Do not include replacement documents in this request.
  • Supply the confirmed DOB in YYYY-MM-DD format. Invalid calendar dates, future dates, and malformed values such as 1990-1001 return HTTP 400. Dates before 1900 are not accepted.
  • The existing BVN or other identity number and identity type cannot be replaced. Contact support for identity-replacement requests.
  • Approved Tier TWO customers must use ONE for information corrections. FULL and TWO submissions cannot replace their approved documents.
  • A successful update does not mean card verification or issuance has completed. If issuance stopped at local date validation, correct the data and retry issuance. If verification was already submitted or reconciliation is required, contact support before retrying.
  • Corrections do not terminate existing cards or change their stored billing address.
The success response remains {"message":"Customer kyc submitted successfully"}.

Non-Nigerian example

Use the customer’s country-specific bank or tax identifier. Swerv normalizes the identifier type to uppercase but does not translate the identifier value.
United Kingdom Tier 1
Supported Tier 2 document types are NIN, PASSPORT, NATIONAL_ID, DRIVERS_LICENSE, VOTERS_CARD, and GHANA_CARD.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Body

application/json
tier
enum<string>
required

ONE submits identity and address information, TWO submits documents after Tier 1, and FULL submits both.

Available options:
ONE,
TWO,
FULL
document
object
information
object

Response

OK

message
string