Provider submission

Sending an authorized instruction to its provider exactly once.

Step by step

Check scope Trader

Before submission, the instruction, counterparty, organization, the trader's scope and the expected revision are checked.
- Scope confirmed
- Updates Instructions, Counterparties, Team members
Submit to provider Trader

The trader submits the authorized instruction to its approved provider. An operation receipt is written under a stable operation key.
- Operation receipted
- Updates Instructions, Operation receipts
Store the provider reference Trader

The provider's instruction ID is recorded as the provider reference and the instruction is marked submitted.
- Authorized → Submitted
- Updates Instructions
Retry safely Trader

A repeat with the same input returns the original result; a repeat with conflicting input is refused.
- Original result returned
- Updates Operation receipts

And how to keep it from happening.

The connection drops after the provider accepted the instruction, and the trader submits again. The operation key returns the first result.
An instruction is submitted on a revision that changed after authorization.
The provider's reference is not stored, so later evidence cannot be matched.

Start free, then use Proto to change fields, steps and approvals before your team goes live.