Recurring billing.

Subscription and instalment billing on card-on-file and DuitNow AutoDebit, with full lifecycle management.

idataraya builds recurring billing systems using two rails that work for Malaysian consumers: tokenized card-on-file (scheme tokens from the card acquirer) and DuitNow AutoDebit (bank account debit mandates). Subscription lifecycle covers sign-up, first payment, subsequent billing cycles, retry on failure, dunning communication, and cancellation. DuitNow AutoDebit mandates are registered through the participating bank and debited on the agreed schedule without requiring the customer to take action each cycle. Card-on-file tokens are stored at the acquirer or scheme level, so PAN never re-enters your system after the initial consent capture.

Card-on-file using acquirer or scheme tokens, no PAN stored
DuitNow AutoDebit mandate registration and scheduled debit
Subscription lifecycle: sign-up, retry, dunning, and cancellation
Reconciliation covers both rails in one consolidated billing report

Book a discovery call

Recurring billing cycleCard-on-file and AutoDebit

Running

Sign-upconsent and tokenFirst paymentT+0Billing cyclescheduledRetry or dunningon failureSettleT+1 per rail

Both rails reconciled in one daily billing report

RECUR-RECON, 01 JunRecurring billing reconciliation

Verified

Card-on-file2,104 cycles matched
DuitNow AutoDebit1,842 cycles matched
Failed cycles38 retry queued
Dunning active12 subscribers

Consolidated at 08:00 MYT, failed cycles alerted

COF-TOK, subscriber 8814Card-on-file token

Verified

Token scopeMerchant-scoped scheme token
PAN in system0 records, never stored
Consent recordedSign-up, 14 Apr 2026
Next billing01 Jul 2026, auto

Token refreshed by scheme on expiry

DuitNow AutoDebit mandateRegistration to live billing

Running

Sign-upconsumer consentBank portalmandate registeredMandate activePayNet confirmedDebit cyclescheduled autoSettleT+1 via IBG

Consumer takes no action after initial registration

Recurring billing built on the rails Malaysian consumers actually use.

Card-on-file and DuitNow AutoDebit are the two recurring payment rails with broad Malaysian consumer and bank support. Building on both covers the consumer segments each rail serves without requiring the consumer to maintain a separate payment method for subscriptions.

Card-on-file with token, not PAN.

On first payment, the card is tokenized at the acquirer or scheme. Subsequent billing cycles submit the token directly, with no cardholder interaction required. The token is scoped to your merchant and the cardholder's consent is recorded at sign-up. PAN does not re-enter your system at any billing cycle.

COF-TOK, subscriber 8814Card-on-file token

Verified

Token scopeMerchant-scoped scheme token
PAN in system0 records, never stored
Consent recordedSign-up, 14 Apr 2026
Next billing01 Jul 2026, auto

Token refreshed by scheme on expiry

DuitNow AutoDebit for bank account subscribers.

DuitNow AutoDebit mandates are registered once through the consumer's internet banking session. The mandate authorises your system to debit the account on the agreed schedule. No card number is involved, and the consumer does not need to take any action at each billing cycle. Participating banks include all major Malaysian institutions.

DuitNow AutoDebit mandateRegistration to live billing

Running

Sign-upconsumer consentBank portalmandate registeredMandate activePayNet confirmedDebit cyclescheduled autoSettleT+1 via IBG

Consumer takes no action after initial registration

Retry and dunning on failed cycles.

When a billing cycle fails (insufficient funds, expired card, mandate suspended), the system applies a configurable retry schedule before escalating to dunning. Dunning sends communication to the subscriber through configured channels. After the dunning window, the subscription transitions to a cancelled or paused state based on your business rules.

Failed billing retry flowCycle failure to resolution

Running

Cycle failsinsufficient fundsRetry 1D+1Retry 2D+3Dunningnotify subscriberCancel or pauseper rules

Retry and dunning schedule configurable per plan

Billing reconciled across both rails.

Card-on-file and DuitNow AutoDebit settlements arrive through different channels on different timelines. The reconciliation engine matches both against your subscription billing log, surfaces failed cycles that did not generate a settlement event, and produces a consolidated billing report covering all subscribers regardless of rail.

RECUR-RECON, 01 JunRecurring billing reconciliation

Verified

Card-on-file cycles2,104 matched, MYR 184k
DuitNow AutoDebit1,842 matched, MYR 162k
Failed cycles38 retry queued
Dunning active12 subscribers

Consolidated billing report at 08:00 MYT

Recurring billing across card-on-file and DuitNow AutoDebit.

Card-on-file billing
Tokenized card-on-file implementation using acquirer or scheme tokens. Subsequent billing cycles use the token with no cardholder interaction and no PAN stored beyond the initial consent capture.
DuitNow AutoDebit integration
Mandate registration flow through participating banks and scheduled debit submission via PayNet. Mandate status tracking and suspension handling included.
Subscription lifecycle engine
Sign-up, first payment, recurring cycle management, configurable retry schedule, dunning communication, and cancellation or pause logic, all driven from one billing service.
Billing reconciliation
Daily reconciliation across card-on-file and AutoDebit settlements, with failed-cycle tracking and a consolidated subscriber billing report.