Skip to main content
Version: 2019-05-29 (Current)

Verify a recipient

Manually verify a recipient's bank account. This endpoint is primarily used for testing purposes as most recipients are automatically verified upon creation.


๐Ÿ”‘API Credentials

Request Parametersโ€‹

Required - 1 fieldRequired Parameters
โ–ผ
`id`STRING(required)
Recipient ID (e.g., recp_test_...). Provided in the URL path.
Example:"recp_test_5xuy4w91xqz7d1w9u0t"

Responsesโ€‹

200

Successful transaction

Recipient verified successfully. Returns the updated recipient object with verified: true.

Verification attributes:
  • verified - Set to true after successful verification
  • verified_at - Timestamp when verification completed
  • failure_code - null if verification succeeded
  • Recipient can now receive transfers

401

Unauthorized

Authentication failed. Invalid or missing API key.

Common causes:
  • Missing Authorization header
  • Invalid secret key
  • Using public key instead of secret key
  • Incorrect HTTP Basic Auth format

404

Not found

Recipient not found.

Common causes:
  • Invalid recipient ID
  • Recipient does not belong to your account
  • Recipient has been deleted
  • Mixing test and live mode IDs

422

Unprocessable entity

Verification failed or recipient already verified.

Common causes:
  • Recipient already verified
  • Bank account verification failed
  • Invalid bank account details

Code samplesโ€‹

curl https://api.omise.co/recipients/recp_test_5xuy4w91xqz7d1w9u0t/verify \
-X PATCH \
-u skey_test_5xuy4w91xqz7d1w9u0t:

Important notesโ€‹

  • Most recipients are automatically verified upon creation
  • This endpoint is primarily for testing purposes
  • Verified recipients can immediately receive transfers
  • Verification typically takes 1-2 business days for live mode
  • In test mode, verification is instant with this endpoint

Try it outโ€‹

Required - 1 fields
โ–ผ