Integration Flow

End-to-End Platform Flow

How a transaction travels through Straventa — from POS or marketplace checkout, through the Payment Gateway, into FDS and AML for risk, and finally into the Reconciliation Engine for settlement.

Platform Architecture

End-to-End Platform Flow

From the till to the bank statement — every transaction passes through risk, monitoring, and reconciliation without any glue code on your side.

Hop by hop

What crosses each boundary

Every product handoff is a clean, signed payload. No magic, no hidden coupling.

Hop 1

PG FDS

Every authorization is passed synchronously to FDS for sub-100ms scoring. The PG holds the customer at the spinner only as long as the FDS rule engine takes — typically under 50ms — then proceeds, flags, or blocks based on the returned decision.

Payload fields (8)
transaction_idmerchant_idamountcurrencypayment_methodcustomer_fingerprintdevice_signalip_address
Hop 2

PG AML

Every transaction is also published asynchronously to AML for typology evaluation against PPATK rules — structuring, layering, placement — without blocking the customer-facing flow. Suspicious patterns surface as cases in the AML queue.

Payload fields (9)
transaction_idmerchant_idamountcurrencycounterparty_accountcustomer_idkyc_tiertransaction_typetimestamp
Hop 3

FDS Recon

Once FDS approves and PG settles, the transaction is forwarded to Reconciliation. The recon engine ingests the settlement record alongside the matching bank statement line and applies per-merchant MDR.

Payload fields (8)
transaction_idmerchant_idgross_amountmdr_amountnet_amountsettlement_datefds_decisionsettlement_currency
Hop 4

AML Recon

AML flags any settled transactions that later trigger a typology — including delayed-pattern alerts. Reconciliation receives these flags and tags the corresponding settlement line so the finance team can hold disbursement until cleared.

Payload fields (7)
transaction_idmerchant_idsettlement_idalert_typeppatk_typologycase_statusopen_date
Every hop is logged to the Reconciliation Engine's 7-year immutable audit trail.

Why this matters

  • No vendor stitching — FDS, AML, and Reconciliation share a transaction model so handoffs are zero-config.
  • Every payload is signed and idempotent — replays are free, double-processing is impossible.
  • Drop in any layer standalone — start with PG, add FDS later, or run Reconciliation against a third-party gateway.
  • Every event is captured in the same audit trail, regulator-ready out of the box.

Ready to wire it up?

Talk to our team about a unified rollout, or drop in just the layer you need.

Ready to automate your financial operations?

Join fintechs and banks across Indonesia who trust Straventa for their compliance and risk operations.