Help Center/Admin Operations/Assign an unmatched incoming payment to a payment intent
Admin Operations•Last updated: 2026-10-20•5 min read

Assign an unmatched incoming payment to a payment intent

The Unmatched Incoming Payments Queue lists funds that reached the treasury with no matching intent. "Assign Intent" links one to the right intent after re-verifying the transaction.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the queue

Open "Finance & Payments" then "Unmatched Payment Exceptions". An empty queue reads "No unmatched incoming transactions in queue."

2

Identify the transfer

Each row shows the record ID, shortened transaction hash, amount and asset, the sender and the block.

3

Find the intent

Find the payment intent ID (it starts with pi_) from the member's request or the Verification Queue.

4

Click "Assign Intent"

A prompt "Enter Target Payment Intent ID (e.g. pi_...):" appears. Type the ID and confirm.

5

Check the result

On success the row leaves the list. On failure an alert shows the server message (for example when the transaction does not satisfy that intent).

6

Reload

Click "Refresh" to see the current queue.

Expected Operational Outcome

The transaction is re-verified against the intent and, if it passes, marked MATCHED (match type MANUAL) and removed from the queue. The match is recorded under your own signed-in account; the page does not send or accept an actor.

Troubleshooting & Failure Modes

Symptom: An alert with an error after assigning
Likely Cause: The unmatched record or the intent was not found, or the on-chain check failed for that intent.
Resolution: Verify the intent ID and amount; try the correct intent.

Was this guide helpful?

Help us refine our platform documentation