Destination confirmation: what the system of record says
An agent's own telemetry says what the agent says it did. Destination confirmation adds a second, independent statement: what the system the agent acted on (for example the payment provider) recorded about the same action. Provantix compares the two and says whether they agree. This page is the one place that explains the states, what makes an action pending or unverified, and what none of it shows.
It runs only for the actions in a reconciled scope: one kind of action (a tool or action type, for example issue_refund) on one system, checked against one destination connection. Everything outside a scope stays self-reported only, and the product says so. To set one up, see Connect Razorpay as a destination.
In the product
Product capture, 15–16 November 2026. Open the image for full size. Counts and dates are examples from the captured workspace.
Open Connectors, then Destination systems. This example has no destination connection, so run outcomes remain agent-reported. A connection is a prerequisite for independent confirmation; it does not itself prove any action matched.
The five states
Each action in a scope has exactly one state at a time, and a reason in words. There is no single score.
| State | What it says | What changes it |
|---|---|---|
| Destination-confirmed | The destination's own record matches the claim: the payment, the amount, the currency and the outcome. The destination's own status is shown beside it, because recorded is not the same as settled. | A later reversal, dispute or status change is recorded beside it as a new result. It never overwrites this one. |
| Conflicting | The destination recorded something different (the amount, the outcome, two records for one action), or the record the agent cited is proven not to exist, on a second look. The reason names what differs. | The difference being explained or corrected at the destination or in the agent's record. A person can record a decision about it. |
| Pending | Too soon to expect the destination's record, or the collection does not yet reach the action. It is never treated as a failed action. | The record arriving, or the pending period ending (24 hours after the claim by default), after which it becomes unverified. |
| Unverified | No unique matching record, or the destination was not collected for the period, or the connection was revoked. This is not evidence that the action did not happen. | A destination record that carries the action id, a refund id the destination can be asked about, or a completed collection of the period. |
| Agent-reported | The agent made the claim and nothing has been collected from the destination yet. | The first collection. |
The history is kept: when pending becomes confirmed, or a confirmed refund later fails, both results stay.
How an action is matched
In order, and the method is shown for every result:
- By the refund id the agent cited. A direct lookup of that id is the destination's own answer on whether it exists. A "no such record" answer only becomes a conflict on a second look at least the delay tolerance apart, never on the first.
- By the action id the agent put in the destination's record (
provantix_action_idin the refund's notes). Two destination records for one action id is a conflict. - By the same payment, amount and time. This is weaker and says so. If more than one record fits, or more than one claim fits the same record, the result is unverified (ambiguous): Provantix does not guess.
What makes an action pending or unverified
- Pending: the claim is recent, or the collection from the destination has not yet reached the time of the claim.
- Unverified: nothing matched in a period the destination was collected for completely, or the destination could not be read, or the connection was revoked or rejected. Only a collection that finished without an error counts as covering a period. A destination that is down, slow or throttled is shown as health on the Connectors page and records a period as not collected. It is never a finding about the agent.
An action with no destination record in a collected period is unverified, never a failed action. Absence found by search is not evidence.
Later outcomes
A reversal, a retry, a dispute, a reopened ticket or a human override is a later fact about an action. It is attached to the action as its own dated entry and shown in time order on the run view. The action's record, its hashes and its result are not changed. A link records that something happened later. It does not say the agent was wrong. See One run, as a chain.
Approvals: present versus covers the action
An approval being present is not the same as it covering the action. Where an approval says what it was given for (the target, an amount limit, an expiry, the policy version), Provantix shows the two apart: approval present and authority verified. See Approvals.
Changes nobody claimed
Reconciling from the destination's side lists changes the destination holds, in a period it was collected for completely, that no agent claimed. The cause is not known and is not guessed. See A change nobody claimed.
Where you see it
- Run view: each action's state, how it matched, the collection window, and what would change it. One run, as a chain.
- Coverage: the destination-confirmed share per scope, the three unresolved groups, and the changes nobody claimed. Coverage.
- Brief and Home: a destination that contradicts a claim is attention; pending past the delay or unverified is watch. Reading the Home page.
- Investigate: the field Destination check filters to each state.
- Exports:
reconciliation.jsoncarries the results, the destination records they rest on and where those came from. The verifiers check it. How verification works.
What it does not show
- That the destination's record is true. It is the destination's own statement. Provantix compares it with the agent's claim and says whether they agree.
- What happened outside the scope. A statement is limited to the scope, the period and the window that were actually collected, and always says so. It does not rule out anything outside them.
- That an action was right. A confirmed refund can still be a refund nobody should have made. Provantix records and compares. It does not judge.
- That the person who approved it was the right person, or that the approval process was sound.
- Anything outside a scope. For those actions the evidence is still the agent's own report, and the product says so.
