Use this endpoint to confirm that an account_id exists before routing funds or creating a payment flow around that account.
Request
API key ID assigned to the integration
RFC3339 timestamp used in the HMAC signature
Hex-encoded HMAC-SHA256 of the request
Body Parameters
OLIVE account ID to verify
Response
Whether the verification request completed successfully
Whether the account exists
Verification result message
Echo of the requested account ID
Example
BODY='{"account_id":"acc_12345678"}'
TIMESTAMP='2026-03-10T12:00:00Z'
SIGNATURE=$(printf 'POST\n/api/v1/payment/verify-account\n%s\n%s' "$TIMESTAMP" "$BODY" | openssl dgst -sha256 -hmac "$OLIVE_HMAC_SECRET" -hex | sed 's/^.* //')
curl -X POST "https://olive-gateway-a6ba.onrender.com/api/v1/payment/verify-account" \
-H "X-API-Key-ID: $OLIVE_API_KEY_ID" \
-H "X-Timestamp: $TIMESTAMP" \
-H "X-Signature: $SIGNATURE" \
-H "Content-Type: application/json" \
-d "$BODY"
{
"success": true,
"exists": true,
"message": "Account verified",
"account_id": "acc_12345678"
}
| Status | Code | Description |
|---|
| 400 | Validation or business error | Invalid payload or account not found |
| 401 | HMAC auth error | Missing/invalid X-API-Key-ID, X-Timestamp, or X-Signature |
| 500 | Internal error | Server error |
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
API key ID assigned to the integration
RFC3339 timestamp used in the HMAC signature
Hex-encoded HMAC-SHA256 of the request
OLIVE account ID to verify
Whether the verification request completed successfully
Whether the account exists
Verification result message
Echo of the requested account ID