02 / Fiat settlement

FIAT PAYMENTS.
TRACEABLE RECORDS.

Explore software workflows for fiat-money payments and bank transfers, with institution-confirmed posting and reconciliation. No physical cash handling.

Fiat payment integration

Six steps from instruction to reconciliation

This illustrative workflow connects fiat bank-transfer instructions with institution-confirmed payment records. Payment availability, execution and timing depend on the participating institutions and applicable requirements.

  1. 01

    Payment request

    A business prepares a fiat payment instruction for its financial institution.

  2. 02

    Secure instruction

    A signed, idempotent transfer instruction is sent over mTLS.

  3. 03

    Receiving ledger

    The receiver validates the beneficiary, screening and limits.

  4. 04

    Institution processing

    Financial institutions execute the authorised payment and update account records.

  5. 05

    Confirmation

    The receiver returns authenticated evidence from its own ledger.

  6. 06

    Reconciled

    The software matches amount, currency and references against confirmed payment records.

Fiat money, not physical cash. These workflows concern bank-account balances in conventional currencies such as USD and THB. DWIN Intertrade provides payment technology and integration; it does not collect, transport, accept deposits of, or pay out physical cash.

The evidence behind every entry

Not just a message.
A balanced ledger.

Our payment software tracks fiat bank-transfer instructions and debit and credit records, then matches institution-confirmed evidence for reconciliation.

Explore the settlement process
Instruction · DWP-20261103-000184 Settled
DR Originating institutionFiat payment · bank account record 250,000.00 USD
CR Receiving institutionBeneficiary ledger · BIC/IBAN verified 250,000.00 USD
  1. Instruction signed & received
  2. Screening & limits passed
  3. Credit posted by receiver
  4. Evidence returned · reconciled
Illustrative example of a fiat bank-transfer record and its evidence trail, not an actual customer transaction or a promise of processing time.
Integration responsibilities

Payment instructions and confirmed records

A notification reports a payment event. A payment integration can also submit an instruction to an institution, track its status and reconcile the resulting records.

An API response alone does not prove that funds have moved. Payment execution and finality are determined by the relevant financial institutions, not by the software's acknowledgement.

AttributeNotification APIDwin payment integration
PurposeReport payment eventsSubmit instructions and reconcile records
ExecutionReported by the providerControlled by participating financial institutions
TriggerPayment status eventAuthorised fiat payment instruction
AccountingEvent data for downstream systemsInstitution-confirmed debit / credit records
OutcomeStatus notificationMatched payment records or an exception for review
Typical useReporting incoming paymentsFiat payment workflow and reconciliation
Information & resources

Your next connection.
Start with the right information.

Explore our service scope and technical information, or contact us to discuss your fiat payment integration.

Documentation enquiries

Public downloads are temporarily unavailable while documentation is updated. Contact us for current service information and applicable due diligence requirements.

Request information
The next connection starts here

LET'S BUILD
WHAT'S NEXT.

Bring your institution, your ambition
and your next challenge.

Start a conversation