Skip to main content
Available on the production API. Confirm sandbox availability separately with Swerv.
POST /customers/{id}/card-verification For individual non-Nigerian customers requesting DEFAULT USD cards, submit the customer’s saved KYC for document verification. First save complete customer KYC, including a supported identity document and the actual residential address. The customer must belong to your authenticated business. No request body is required. This operation does not create a card, reserve funds, or debit a wallet. Nigerian customers continue using synchronous verification through POST /cards.
HTTP 202 means verification is pending:
An already approved, unchanged verification returns HTTP 200 with status: "APPROVED" and can_create_card: true. Repeated submissions reuse the existing verification; do not change customer details to force a new attempt. Validation failures return 422; rejected verification or reconciliation requirements return 409. Temporary verification/document availability errors return 503. Errors contain code, message, and optionally field. Subscribe to verification decision webhooks, or poll Get Card Verification at most once per minute. After approval, explicitly call Create Card. Approval does not automatically issue a card. Existing integrations may continue initiating document verification through POST /cards; a pending response does not create or debit a card.