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
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
string
required
The payment claim’s ID (e.g.,
pymt_claim_abc123def456).Response
Approve payment claim
string
required
The payment claim’s ID (e.g.,
pymt_claim_abc123def456).Response
Error when claim is not pending
Reject payment claim
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
- Customer submits a payment claim via a payment claim link.
- Claim appears with
pendingstatus. - Review the claim by checking the transaction on the blockchain.
- Approve the claim (creates a crypto transaction) or reject it with a reason.
- 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.