One invoice, every route priced beside it, and a name against every approval.
Every step leaves a record you can hand to your bank: what you were quoted, who approved it, and what the settlement partner sent back.
A payment instruction is created, approved and submitted only after that decision is on the record, and a route is approved for payment on the same condition. The decision is made in compliance review, outside your workspace, so it stays independent of the people who raise payments.
Every stored invoice has a check behind it. A route comparison reads an invoice once that check comes back clean, and a scan that finds a threat rejects the invoice with a stated reason your team can see.
Each candidate is stored with its rate, its spread and its expiry before you see the comparison, so you can prove afterwards what you were quoted. The saving shown on each route is measured against an indicative bank wire for the same corridor. Approving a route reads its stored quote again and refuses a rate, a currency pair or an expiry that has moved.
Your workspace sets who has to sign. The default puts two approvals on a high-value payment or a stablecoin route, one of them an owner, and the person who raised it is never one of them. One person can sign a payment once, and the database itself holds that limit, so no code path goes around it.
The partner's confirmation is accepted on a signature match inside a five-minute window, recorded once, and only then allowed to move the payment. A payment's status only ever advances, so a late confirmation carrying an earlier status is stored and set aside. One that matches no payment goes to a queue where a person resolves it against the payment it belongs to.
Credstone is a technology company. Its products are software licensed to regulated financial institutions and payment service providers, who operate them under their own authorisations. Credstone does not hold, transmit, exchange, or custody funds or digital assets, and does not provide payment or financial services.
