Recipients

Operations for managing recipient accounts

Create a recipient

post

Create a new recipient for payments. Recipients can have crypto settlement details, fiat settlement details with KYC information, or both.

Authentication

All API requests to orda require HMAC signatures using your project's client ID and client secret. The signature is a HMAC-SHA256 hash of the request body, using your Client Secret as the key. For the endpoints where there is no request body, use an empty string.

Required Headers

Header	Description
x-client-id	Your project's client ID
x-signature	HMAC-SHA256 signature derived from your client secret
Content-Type	application/json for this request

--

Important Notes:

• The cryptoSettlementDetails object contains blockchain settlement information

• The kycInformation object is required for fiatSettlementDetails

• Both kycInformation and fiatSettlementDetails are optional for crypto-only transactions

• You need a project client ID to create recipients

Authorizations

ClientId & Signature & Timestamp

Header parameters

x-client-idstringRequired

Your project client ID from orda dashboard

Default: prj_abc123def456ghi789Example: prj_abc123def456ghi789

x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

Default: a1b2c3d4e5f6789abc123def456ghi789abc123def456Example: a1b2c3d4e5f6789abc123def456ghi789abc123def456

x-timestampstringOptional

Unix timestamp in milliseconds for replay protection (recommended)

Default: 1704067200000Example: 1704067200000

Body

application/json

namestringRequired

Name of the recipient

Example: Leeroy Jenkins

Responses

201

Recipient created successfully

application/json

400

Bad Request - Invalid parameters

application/json

401

Unauthorized - Invalid client ID

application/json

404

Not Found - Project not found

application/json

409

Conflict - Recipient with same name already exists

application/json

422

Unprocessable Entity - Invalid data format

application/json

429

Too Many Requests

application/json

500

Internal Server Error

application/json

post

/create-recipient

HTTPcURLJavaScriptPython

POST /v1/create-recipient HTTP/1.1
Host: api.orda.network
x-client-id: prj_abc123def456ghi789
x-signature: a1b2c3d4e5f6789abc123def456ghi789abc123def456
x-timestamp: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 181

{
  "name": "DeFi Protocol",
  "cryptoSettlementDetails": {
    "toChain": "8453",
    "toToken": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "toAddress": "0x742d35Cc6634C0532925a3b844Bc45426438f000"
  }
}

Crypto-only recipientFiat settlement recipient

{
  "message": "Recipient created successfully",
  "recipientId": "generated-recipient-id"
}

Update recipient details

put

Update an existing recipient's settlement details.

Authentication

All API requests to orda require HMAC signatures using your project's client ID and client secret. The signature is a HMAC-SHA256 hash of the request body, using your Client Secret as the key. For the endpoints where there is no request body, use an empty string.

Required Headers

Header	Description
x-client-id	Your project's client ID
x-signature	HMAC-SHA256 signature derived from your client secret
Content-Type	application/json for this request

---

Important Notes:

• The recipient ID will remain the same despite settlement details changing

• The response includes previously stored settlement details for audit trail

• You need the project's client ID to update recipients

Authorizations

ClientId & Signature & Timestamp

Header parameters

x-client-idstringRequired

Your project client ID from orda dashboard

Default: prj_abc123def456ghi789Example: prj_abc123def456ghi789

x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

Default: a1b2c3d4e5f6789abc123def456ghi789abc123def456Example: a1b2c3d4e5f6789abc123def456ghi789abc123def456

x-timestampstringOptional

Unix timestamp in milliseconds for replay protection (recommended)

Default: 1704067200000Example: 1704067200000

Body

application/json

recipientIdstringRequired

ID of the recipient to update

Responses

200

Recipient updated successfully

application/json

400

Bad Request - Invalid parameters

application/json

401

Unauthorized - Invalid client ID

application/json

404

Not Found - Recipient not found

application/json

422

Unprocessable Entity - Invalid data format

application/json

429

Too Many Requests

application/json

500

Internal Server Error

application/json

put

/update-recipient

HTTPcURLJavaScriptPython

PUT /v1/update-recipient HTTP/1.1
Host: api.orda.network
x-client-id: prj_abc123def456ghi789
x-signature: a1b2c3d4e5f6789abc123def456ghi789abc123def456
x-timestamp: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 190

{
  "recipientId": "recipient-12345",
  "cryptoSettlementDetails": {
    "toChain": "8453",
    "toToken": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "toAddress": "0x742d35Cc6634C0532925a3b844Bc45426438f000"
  }
}

Update crypto settlement detailsUpdate fiat settlement details

{
  "message": "Recipient details updated successfully",
  "previousDetails": {}
}

Deactivate a recipient

put

Deactivate a recipient to prevent it from processing further transactions. Existing transactions will not be affected.

Authentication

All API requests to orda require HMAC signatures using your project's client ID and client secret. The signature is a HMAC-SHA256 hash of the request body, using your Client Secret as the key. For the endpoints where there is no request body, use an empty string.

Required Headers

Header	Description
x-client-id	Your project's client ID
x-signature	HMAC-SHA256 signature derived from your client secret
Content-Type	application/json for this request

---

Important Notes:

• Only the business can deactivate their recipients

• Deactivation can be undone by the business at any time using the /reactivate-recipient endpoint

• New transactions using the deactivated recipient's ID will be rejected

Authorizations

ClientId & Signature & Timestamp

Header parameters

x-client-idstringRequired

Your project client ID from orda dashboard

Default: prj_abc123def456ghi789Example: prj_abc123def456ghi789

x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

Default: a1b2c3d4e5f6789abc123def456ghi789abc123def456Example: a1b2c3d4e5f6789abc123def456ghi789abc123def456

x-timestampstringOptional

Unix timestamp in milliseconds for replay protection (recommended)

Default: 1704067200000Example: 1704067200000

Body

application/json

recipientIdstringRequired

ID of the recipient to deactivate

Responses

200

Recipient deactivated successfully

application/json

400

Bad Request - Missing recipient ID

application/json

401

Unauthorized - Invalid API key

application/json

404

Not Found - Recipient not found

application/json

429

Too Many Requests

application/json

500

Internal Server Error

application/json

put

/deactivate-recipient

HTTPcURLJavaScriptPython

PUT /v1/deactivate-recipient HTTP/1.1
Host: api.orda.network
x-client-id: prj_abc123def456ghi789
x-signature: a1b2c3d4e5f6789abc123def456ghi789abc123def456
x-timestamp: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 33

{
  "recipientId": "recipient-12345"
}

{
  "message": "Recipient deactivated successfully",
  "recipientName": "Example Recipient",
  "deactivatedAt": "2024-03-19T12:34:56.789Z"
}