One gateway over the systems the institution already runs

The gateway is the composition layer over the institution's existing payment, account and customer APIs. Every merchant sits in one register with one MID, whether it runs links only or the full gateway, and every transaction from every method and product is in one list.

• The settlement run and the e-invoice state on every transaction
• Each transaction a timeline with clocks, from the checkout session to the webhook
• Declines with the reason class: issuer, risk or bank down
• Scheduled reports, including the Bank Negara acquiring return

Cards, DuitNow QR, FPX and e-wallets, each with its approval rate and latency on screen. Routing is a rule table the institution owns, with a fallback where a rule needs one and the rule that is firing now shown as such.

• A card routed to a fallback processor after timeouts
• A slow FPX bank announced on the checkout, with DuitNow QR offered
• A wallet hidden for a set time when its error rate climbs

One settlement run a day across every rail. One person prepares it, a second approves it, and the files go on the second approval. The scheme and rail files are read back and reconciled against the ledger on the same screen as the run.

• Gross, fees, SST, held and net per merchant per run
• Returned credits reissued to a corrected account
• Versioned fee schedules, with rail costs and margin beside them
• SST on fees on every merchant statement, exported to the ledger

The merchant answers a dispute in the portal with evidence, and the institution reviews it on one screen: the claim, the merchant's answer, the deadline at the top and the decision to take.

• Represent to the issuer, accept and debit the merchant, or ask for more
• The merchant's dispute history beside the decision
• The dispute rate against the scheme threshold

asasii smart terminals, countertop devices and unattended readers in toll lanes, vending machines, car park exits and kiosks accept DuitNow QR, cards and the major Malaysian e-wallets, provisioned and monitored as one fleet.

• Remote provisioning and configuration
• Key and app updates
• Health monitoring across the terminal and soundbox estate, from one console