Tool sheet · PaymentChannelClaim

Claim Payment Channel

transactionactive2 credits

Redeem XRP from a channel with a signed claim, or request/close the channel (tfClose).

What

Settles channel activity on-ledger: the recipient redeems XRP using a signed claim, or either party moves to close the channel.

Why you'd use it

Off-ledger claims are just promises until redeemed. This is where the recipient actually collects — and how either side winds the channel down.

How

Enter the Channel ID.
As the recipient redeeming: enter the claim's Authorized Amount and the New Channel Balance (the running total delivered), plus the Claim Signature and Channel Public Key from the sender's latest claim.
Always redeem the LATEST claim — amounts are cumulative totals, not increments.
To wind down, tick Request Close: the sender's close starts the settle-delay countdown; the recipient's close is immediate once they have redeemed.
Submit and confirm tesSUCCESS.

Watch out

Claim amounts are cumulative. Redeeming an old claim for less forfeits the difference — keep only the newest.
Recipients: redeem before the settle delay runs out after a close request, or unredeemed XRP returns to the sender.
Verify every claim's signature (Verify Channel Claim) before providing goods or services against it.
When a channel closes, leftover XRP goes back to the creator and the reserve is freed.

For example

At the end of the month, the API vendor takes the customer's latest claim — cumulative total 87 XRP — and redeems it in one transaction. Ten thousand micropayments settled for one ledger fee.