Customers
Get Card Verification
Available on the production API; confirm sandbox availability separately. Check a customer belonging to the authenticated business. Poll at most once per minute. Does not create a card or debit a wallet. Submit a new card request only when can_create_card is true; approval does not automatically start issuance.
GET
Available on the production API. Confirm sandbox availability separately with Swerv.
DEFAULT USD card request.
The customer must belong to the business authenticated by your bearer token.
This request does not create a card or debit a wallet.
Poll at most once per minute. A check can reconcile a pending verification;
multiple callers share the same refresh limit. Do not treat an HTTP 200 response
alone as approval: inspect status and can_create_card.
NOT_SUBMITTED, PENDING, APPROVED, REJECTED, and
RECONCILIATION_REQUIRED. Submit a new card request only when can_create_card
is true; issuance does not start automatically after approval.
A typed verification error can return HTTP 503 with code, message, and an
optional field. Preserve the pending UI state when status cannot be retrieved;
use the error code to decide whether to retry later or contact support.
See the complete non-Nigerian KYC flow for
document requirements, correction rules, and safe issuance retries.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Current verification status, not necessarily approval.
Swerv customer ID owned by the authenticated business.
Available options:
NOT_SUBMITTED, PENDING, APPROVED, REJECTED, RECONCILIATION_REQUIRED True when the saved verification permits another issuance attempt. Not a guarantee of successful issuance or sufficient wallet funds.