Overview
DuitNow is listed as instant payment, bank transfer in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.
Role in the payment stack
Payment method / bank transfer
This is mainly a local payment rail or bank-transfer method used by buyers. Merchants normally enable it through a PSP, bank, aggregator, or local acquiring partner.
Merchant usage and connection route
DuitNow QR in the payment stack
DuitNow QR is relevant for merchants selling in Malaysia who need bank-app and wallet QR payment acceptance as part of local checkout or POS coverage. Evaluate it for customer reach, static versus dynamic QR needs, reconciliation references, refund operations, and how it fits beside cards, FPX-style bank payment, wallets, and BNPL.
Connection route
A merchant may access DuitNow QR through a Malaysian bank, acquirer, PSP, gateway, wallet provider, terminal provider, or platform. Confirm whether the provider offers direct merchant QR onboarding or a bundled route, and who controls payment acceptance, reporting, settlement, refunds, and support.
Verification questions
- Is the intended DuitNow QR flow online, in-app, invoice-based, POS, static QR, dynamic QR, or marketplace-based?
- Which bank, acquirer, PSP, gateway, wallet provider, or platform is the merchant route?
- What reconciliation references, callback behavior, refund process, and failed-payment handling are available?
- Does the route support the merchant's Malaysian entity, category, currencies, locations, and order values?
- Who handles payment disputes, payer-bank questions, settlement reports, and operational incidents?
Merchant caveats
- DuitNow QR access depends on the bank, wallet, PSP, or platform relationship.
- Static QR, dynamic QR, online checkout, and terminal use can have different operating needs.
- Reconciliation and refund workflows should be tested before high-volume rollout.
- Provider examples are discovery examples only, not recommendations or support evidence.
Provider examples to verify
Related markets
Keep researching
- PSP contacts in Malaysia
- Payment Channel Directory
- DuitNow vs Touch 'n Go eWallet in Malaysia
- DuitNow vs BigPay Malaysia in Malaysia
- Submit payment requirements
This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.
Sources
What merchants should confirm
- Whether the product is available to merchants incorporated outside the target country.
- Whether a local entity, local bank account, licence, or local tax registration is required.
- Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
- Industry restrictions, reserve policies, onboarding documents, and implementation support.
Merchant eligibility
A local entity, local account, or additional licensing may be required.
Pricing and settlement
Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.
Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.
Capability verification checklist
Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.
- Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
- Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
- Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.
Official links to open
Commercial terms to confirm
| Pricing model | bank transfer or psp priced |
|---|---|
| Pricing basis | provider quote required |
Fields still to confirm
- Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
- FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.
Integration route to confirm
| API / checkout route | psp or bank transfer route |
|---|
Fields still to confirm
- SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
- PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
- 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.
Operational features to confirm
No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.
Fields still to confirm
- Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.