FPX connects your checkout to Malaysia's online banking network, covering both B2C and B2B bank accounts.
FPX is the primary online bank-transfer rail for Malaysian e-commerce and enterprise checkout. The payer authenticates through their bank's online banking interface and authorises a direct debit from their account. FPX B2C covers personal accounts across the participating bank network. FPX B2B extends the same rail to corporate accounts with higher single-transaction limits, making it suitable for wholesale orders, invoice settlement, and supplier payments that exceed the B2C ceiling. idataraya integrates FPX through a licensed payment gateway or direct host-to-host connection, handles the redirect and callback flow, and reconciles settlement files against your transaction log on a T+1 cycle.
FPX B2C and B2B variants, covering personal and corporate accounts
Redirect and direct-post integration modes
T+1 settlement with daily reconciliation against bank settlement files
Callback verification and idempotent transaction state management
FPX looks simple on the surface: the customer picks their bank, logs in, approves. Behind the surface, the integration handles redirects, signed callbacks, settlement file parsing, and reconciliation against your order ledger. We do that part.
Bank selection inside your checkout.
The payer selects their bank from the FPX bank list, authenticates on the bank's page, and lands back on your confirmation screen. The integration manages the redirect lifecycle, verifies the signed response, and updates the order state before the customer sees the result.
MYR 530.00Order #FPX-2204
Choose payment method
FPX Online banking
DuitNow QR
Cards
ENBMRedirects to your bank, returns signed
FPX B2B for higher-value corporate transactions.
FPX B2B uses the same rail as B2C but authenticates against corporate online banking, carries a higher per-transaction limit, and requires the payer to hold a business account at the participating bank. The integration determines which variant to initiate based on the transaction amount and the configured merchant profile.
FPX-B2B, TXN-00814Corporate payment check
Verified
Account typeCorporate, verified
Transaction limitWithin B2B ceiling
Bank authSigned, confirmed
SettlementT+1, 11:00 MYT batch
B2B rail selected, limit not breached
Callback handling and idempotency.
FPX callbacks arrive over HTTP. The integration verifies the message digest, deduplicates retried notifications, and resolves any timing gap between the redirect return and the async callback by holding the transaction in a pending state until the authoritative signal arrives from the bank.
FPX callback, FPX-2204Redirect to confirmed state
Running
Redirectbank portalAuthcustomer approvesResponsedigest verifiedOrder updatedpaid state
Idempotent, duplicate callback ignored
T+1 settlement reconciled automatically.
FPX settles on a T+1 cycle. The integration retrieves the daily settlement file, parses the bank reference numbers, and performs a three-way match against your transaction log and bank statement. Discrepancies are flagged the morning after, not during month-end close.
FPX-RECON, T+1Daily settlement match
Verified
FPX B2C transactions2,104 matched
FPX B2B transactions38 matched
Pending callbacks2 within SLA
Net settledMYR 684k, T+1
Reconciliation complete, 08:10 MYT
FPX integrated and reconciled.
FPX B2C integration
Redirect-based FPX B2C integration with signed callback verification, idempotent state management, and order confirmation flow.
FPX B2B integration
Corporate variant integration with automatic rail selection based on transaction amount and merchant profile configuration.
Settlement reconciliation
Daily T+1 reconciliation between FPX settlement files, transaction log, and bank statement with discrepancy alerting.
Reporting
Per-transaction and daily summary reports broken down by FPX variant, bank, and time period.