Skip to main content
POST
/
v1
/
rfis
/
{id}
/
respond
Respond to an RFI
curl --request POST \
  --url https://api.antonpayments.com/v1/rfis/{id}/respond \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "response": "<string>",
  "document_ids": [
    "<string>"
  ]
}
'
{ "id": "<string>", "merchant_id": "<string>", "status": "open", "category": "<string>", "urgency": "low", "entity_type": "payout", "entity_id": "<string>", "source": "internal", "subject": "<string>", "description": "<string>", "questions": [ "<string>" ], "created_at": "2026-04-15T14:30:00Z", "provider": "<string>", "provider_ref": "<string>", "response": "<string>", "responded_at": "2026-04-15T14:30:00Z", "document_ids": [ "<string>" ], "resolved_at": "2026-04-15T14:30:00Z", "resolution_note": "<string>", "outcome": "cleared", "due_at": "2026-04-15T14:30:00Z" }

Authorizations

​
Authorization
string
header
required

API keys are opaque strings prefixed by environment:

  • ak_live_* — production keys, accepted only on api.antonpayments.com.
  • ak_test_* — sandbox keys, accepted only on api.antonpayments.dev.

Include your key in the Authorization header: Bearer ak_test_....

Path Parameters

​
id
string
required
Pattern: ^rfi_[a-zA-Z0-9]+$

Body

application/json
​
response
string
required

Free-form text response answering the RFI's questions.

​
document_ids
string[]

IDs of supporting documents uploaded via POST /v1/documents.

Pattern: ^doc_[a-zA-Z0-9]+$

Response

Response recorded. RFI moves to responded pending ops review.

A Request for Information raised by Anton's compliance team. Each RFI asks specific questions about a payout, beneficiary, or merchant and typically gates a held transaction until resolved.

​
id
string
required
Pattern: ^rfi_[a-zA-Z0-9]+$
​
merchant_id
string
required
Pattern: ^mer_[a-zA-Z0-9]+$
​
status
enum<string>
required
Available options:
open,
responded,
resolved,
escalated
​
category
string
required

Compliance category (e.g. source_of_funds, identity_verification).

​
urgency
enum<string>
required
Available options:
low,
medium,
high
​
entity_type
enum<string>
required
Available options:
payout,
beneficiary,
merchant
​
entity_id
string
required
​
source
enum<string>
required
Available options:
internal,
merchant,
external
​
subject
string
required
​
description
string
required
​
questions
string[]
required
​
created_at
string<date-time>
required

RFC 3339 / ISO 8601 timestamp in UTC.

Example:

"2026-04-15T14:30:00Z"

​
provider
string

Upstream rail/system that originated the RFI, if any.

​
provider_ref
string
​
response
string

Merchant's submitted response text.

​
responded_at
string<date-time>

RFC 3339 / ISO 8601 timestamp in UTC.

Example:

"2026-04-15T14:30:00Z"

​
document_ids
string[]
Pattern: ^doc_[a-zA-Z0-9]+$
​
resolved_at
string<date-time>

RFC 3339 / ISO 8601 timestamp in UTC.

Example:

"2026-04-15T14:30:00Z"

​
resolution_note
string
​
outcome
enum<string>
Available options:
cleared,
blocked
​
due_at
string<date-time>

RFC 3339 / ISO 8601 timestamp in UTC.

Example:

"2026-04-15T14:30:00Z"