Verify a recipient

PATCHhttps://api.omise.co/recipients/:id/verify

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

---

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.

Returned recipient attributes:

• object - The value "recipient"
• id - Recipient identifier (recp_*)
• livemode - Live or test mode
• location - API path to the recipient object
• activated_at - Activation timestamp (ISO 8601)
• active - Whether recipient is active
• bank_account - Destination bank account object
• created_at - Creation timestamp (ISO 8601)
• default - Whether recipient is account default
• deleted - Whether recipient is deleted
• description - Recipient description
• email - Recipient email address
• failure_code - Failure reason code (name_mismatch, account_not_found, bank_not_found)
• metadata - Custom metadata
• name - Recipient name
• schedule - Transfer schedule (expandable)
• tax_id - Recipient tax ID
• type - Recipient type (individual, corporation)
• verified - Whether recipient is verified
• verified_at - Verification timestamp (ISO 8601)

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

5xx

Server error

Server-side error occurred. These are rare but should be handled gracefully.

How to handle:

• Retry the request with exponential backoff
• Check status.omise.co for service incidents
• See Error Handling for detailed guidance

---

Code samples

cURL

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

Ruby

require 'omise'

Omise.api_key = 'skey_test_5xuy4w91xqz7d1w9u0t'

recipient = Omise::Recipient.verify('recp_test_5xuy4w91xqz7d1w9u0t')

Python

import omise

omise.api_secret = 'skey_test_5xuy4w91xqz7d1w9u0t'

recipient = omise.Recipient.verify('recp_test_5xuy4w91xqz7d1w9u0t')

Node.js

const omise = require('omise')({
  secretKey: 'skey_test_5xuy4w91xqz7d1w9u0t'
});

const recipient = await omise.recipients.verify('recp_test_5xuy4w91xqz7d1w9u0t');

PHP

<?php
define('OMISE_SECRET_KEY', 'skey_test_5xuy4w91xqz7d1w9u0t');

$recipient = OmiseRecipient::retrieve('recp_test_5xuy4w91xqz7d1w9u0t');
$recipient->verify();

Java

Client client = new Client.Builder()
    .secretKey("skey_test_5xuy4w91xqz7d1w9u0t")
    .build();

Recipient recipient = client.recipients()
    .verify("recp_test_5xuy4w91xqz7d1w9u0t");

C#

var client = new Client("skey_test_5xuy4w91xqz7d1w9u0t");

var recipient = await client.Recipients.Verify("recp_test_5xuy4w91xqz7d1w9u0t");

Go

client, _ := omise.NewClient(
    "pkey_test_5xuy4w91xqz7d1w9u0t",
    "skey_test_5xuy4w91xqz7d1w9u0t",
)

recipient, _ := client.Recipients().Verify("recp_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

---

🔑API Credentials

▼

Try it out

Required - 1 fields

▼

id(Required)

Your IP: ...Loading...