Launch integration scope

Commerce and settlement evidence, connected with purpose.

Dinty is designed around a focused launch topology: Shopify provides the commerce truth, while Shopify Payments and Kustom provide supported settlement evidence.

These integrations describe the approved launch scope. Live production connections remain gated until Dinty's readiness and pilot approvals are complete.

Commerce authority

Shopify

Provides the launch commerce evidence Dinty needs to understand what happened at the webshop.

  • Stores and orders
  • Order lines and refunds
  • Payment activity and references
  • Multiple connected stores

Native settlement evidence

Shopify Payments

Contributes supported account, payout, balance-transaction, fee, and dispute evidence through the Shopify connection.

  • Payouts and statuses
  • Balance transactions
  • Fees and net components
  • Disputes where accessible

External settlement provider

Kustom

Adds separately connected payout and transaction evidence for supported Kustom settlement flows.

  • Payout summaries
  • Payout details
  • Transaction rows
  • Corrections and provider components

Purposeful routing

Provider labels never decide where money belongs.

Dinty records the expected store, gateway, and settlement-account relationship explicitly. Tenant ownership and financial identity never come from an unverified provider name.

Illustrative route

Nordic Store
→ Kustom account

Versioned Dinty routing policy defines the expected destination for this payment flow.

Route evidenceConfigured

Commerce source

Shopify store · Nordic Store
Connected

Payment gateway

Supported provider reference namespace
Kustom

Expected account

Workspace-authorized settlement account
EUR · 0418

Routing result

Exact scope and version retained
Ready
✓
One explicit routeProvider display names alone do not establish the link.

Graceful limitations

A missing permission is never presented as an empty financial result.

Dinty tests capabilities independently and limits only the affected explanation when a provider feature is unavailable.

01

Capability-aware

Order history, payouts, disputes, currencies, and schedules are verified separately.

02

Freshness-aware

Polling coverage and webhook health remain visible alongside the financial result.

03

Fail-closed

Authorization errors and unknown provider meanings block unsafe certification.