Skip to main content
This API allows you to view, approve, and reject cryptocurrency payment claims submitted by customers.

The payment claim object

string
Unique identifier with pymt_claim_ prefix (e.g., pymt_claim_abc123def456).
string
Always "payment_claim".
string
Claim status: pending, approved, or rejected.
string
Claimed transaction amount.
string
Blockchain transaction hash provided by customer.
string
Reason for rejection. null if not rejected.
string
When the claim was approved or rejected (ISO 8601). null if pending.
string
The customer who submitted the claim.
string
Currency code (e.g., BTC, ETH).
string
The receiving address ID.
string
The receiving address.
integer
User ID who approved or rejected. null if pending.
string
Created transaction ID. null if not approved.
string
When the claim was submitted (ISO 8601).
string
When the claim was last updated (ISO 8601).

List payment claims

Retrieves a paginated list of all payment claims in your account. Claims are ordered by creation date (newest first).
integer
default:"1"
Page number for pagination. Results are returned 25 items per page.
string
Filter by status. One of: pending, approved, rejected.

Filtering by status

Response

Get payment claim

Retrieves a specific payment claim by ID.
string
required
The payment claim’s ID (e.g., pymt_claim_abc123def456).
Response

Approve payment claim

Approves a pending payment claim. This creates a corresponding crypto transaction record.
string
required
The payment claim’s ID (e.g., pymt_claim_abc123def456).
Response

Error when claim is not pending

Reject payment claim

Rejects a pending payment claim with an optional reason.
string
required
The payment claim’s ID (e.g., pymt_claim_abc123def456).
string
Reason for rejection. Defaults to "No reason provided" if omitted.
Response

Payment claim statuses

Workflow

  1. Customer submits a payment claim via a payment claim link.
  2. Claim appears with pending status.
  3. Review the claim by checking the transaction on the blockchain.
  4. Approve the claim (creates a crypto transaction) or reject it with a reason.
  5. Approved claims can be allocated to invoices.

Webhooks

The following webhook events are triggered for payment claims:

Sandbox support

The API respects sandbox scoping. If your API token is associated with a sandbox, you can only access claims created in that sandbox. Approved and rejected claims are isolated from production data.