​

Delta Verification Setup

Delta adds an external verification step to matching payment approvals. Conto creates an approval request, sends a signed webhook with the payment and invoice context, waits for the decision, and then lets the payment continue or records the rejection.

​

What To Provide

Prepare the following before onboarding:

• the Conto organization to connect
• the public HTTPS URL of your Delta verification webhook
• a shared HMAC secret for signing and verifying requests
• optional agent references if verification should apply only to selected agents
• a representative vendor and invoice scenario for the first test

​

What Gets Connected

During onboarding, Conto connects three customer-visible pieces:

• an approval workflow that determines which payments require Delta verification
• a signed notification channel that delivers approval requests
• a Delta verification record that keeps the decision, proof reference, and related payment together for reconciliation

You do not need to create these records individually unless your onboarding contact asks you to.

​

Readiness Signals

Delta is ready for a first test when:

• the Delta section appears in the dashboard
• a matching payment request returns REQUIRES_APPROVAL and an approvalRequestId
• your verification service receives a signed approval.requested event
• the Delta detail view records the decision and proof reference after the callback

If any signal is missing, check the workflow scope and webhook delivery, then contact your Conto onboarding contact if the organization still does not appear enabled.

​

Prepare A Test Payment

Before running the end-to-end test, confirm that the organization has:

• an agent included in the workflow scope
• the managed- or external-wallet payment path you intend to use
• an approved counterparty for the vendor address
• payment requests that include context.invoice

Continue with Delta End-to-End Test.

​

Related Docs