Skip to main content

​
Delta Verification Setup

Use this guide when you want Conto to route your organization’s payment approvals through the pilot Delta verification service. Delta sits in the approval step for this pilot. When a matching payment request is created, Conto opens an approval request, sends the pilot Delta verification service a signed webhook with payment and invoice context, and waits for Delta’s decision before the payment continues.
Delta is currently a guided rollout, not a self-serve dashboard toggle. If you want Delta access, contact sales@conto.finance and Conto will activate it for your organization.

​
How To Get Access

If you want Delta enabled for your organization:
  1. Contact sales@conto.finance or your Conto contact.
  2. Share the organization you want to enroll and whether you want Delta scoped to specific agents.
  3. Share the public webhook URL for the pilot Delta verification service and the HMAC secret you want Conto to use.
  4. Conto activates Delta for your organization and confirms when it is ready for testing.

​
What Conto Activates For You

When Conto enables Delta for an organization, we set up Delta for that org:
  • Turns on Delta for the organization
  • Sets up the approver identity Delta uses for verification decisions
  • Creates or updates the delta approval workflow
  • Creates or updates the Delta webhook notification channel
You do not need to provision those pieces manually.

​
What You Need To Provide

For most onboardings, Conto only needs:
  • The organization you want activated
  • The public pilot verification service webhook URL, for example https://delta-verifier.example/webhooks/conto/approval
  • A shared HMAC secret
  • Optional agent IDs if you want Delta limited to a subset of agents
  • The vendor / invoice scenario you want to test first
This is the public endpoint of your own verification service, the URL Conto sends approval webhooks to for Delta decisions.
Delta webhook targets must resolve to a public address. Loopback, private, and internal-only hosts are rejected by Conto’s webhook safety checks.

​
How To Know Delta Is Active

After Conto activates Delta:
  • The organization’s Delta tab appears in the main dashboard sidebar
  • Matching payment requests return REQUIRES_APPROVAL with an approvalRequestId
  • The pilot Delta verification service receives the signed approval.requested webhook for matching requests
  • Proof metadata appears in the Delta detail view after a Delta verification decision
If Delta does not appear to be active, contact your Conto onboarding contact or sales@conto.finance. Before running a payment through Delta, make sure the target organization also has:
  • An agent that is either in the scoped agent list or intentionally left unscoped
  • A managed wallet or external wallet flow you plan to test
  • An approved counterparty matching the vendor address
  • Payment requests that include context.invoice
For the end-to-end test flow, see Delta Smoke Test.

Delta Smoke Test

Run the managed-wallet and external-wallet Delta flows end to end

Notification Channels

Delta webhook payload format, action tokens, and callback contract

External Approvals

Review the generic approval-channel callback flow and verification block

Payments API

See the SDK request shape, approvalRequestId, and invoice context