One-time passwords, withdrawal alerts, installment reminders, and other service messages are exchanged millions of times every day between banks and their customers. Yet in many banks, the cost of this communication flow, the logic behind each message, and each customer’s share of the overall consumption remain unclear. By introducing a management layer between banking systems and messaging infrastructure, Arad Notification Wallet helps banks transform banking notifications from an undifferentiated expense into a controllable, measurable, and policy-driven service.
According to Arad ITC’s Public Relations Department, banks send millions of messages to their customers every day—from one-time passwords and security alerts to debit and credit notifications, installment due dates, cheque status updates, account balances, and other service messages.
These notifications have become an inseparable part of modern banking. Yet behind this massive communication flow lies a question that many banks still cannot answer precisely:
Exactly which message did the bank pay for, for which customer, for which account, and according to which financial logic?
In a conventional architecture, the banking system generates a message, hands it over to an SMS gateway, and the delivery expense is recorded under a general cost category. At the end of the billing period, the bank knows how many messages were sent and how much it must pay. But it often does not know how much of that cost was unavoidable, how much could have been handled through another channel, which services should have remained free, which could have been monetized, or precisely how much of the expense belonged to each customer, account, event, or source system.
The challenge is not merely the rising cost of SMS. The deeper issue is that, for one of the bank’s most frequently used communication services, many institutions still lack an independent mechanism for financial policy management, consumption control, and precise cost allocation.
With Arad Notification Wallet, Arad has sought to turn this hidden layer in banking messaging architecture into a manageable capability: an intelligent layer that determines, before each notification is sent, whether it should be delivered at all, who should bear its cost, which package or credit source should fund it, and whether SMS is actually the most appropriate delivery channel.
Not All Messages Are the Same
A one-time password cannot be treated the same way as an account balance notification or a low-value transaction alert. A suspicious-login warning is a critical security message, while a periodic account report may be an optional service. Likewise, notifications for a high-transaction corporate account should not necessarily follow the same financial model as messages sent to a low-volume retail customer.
Yet in traditional architectures, all of these messages often enter the same delivery path, with their final cost absorbed collectively by the bank.
Arad Notification Wallet removes this one-size-fits-all logic. Before delivery, each message is treated as a banking event, and the bank can define an independent policy for each type of event:
- One-time passwords and security alerts can be sent at the bank’s expense.
- Optional notification services can be deducted from the customer’s package or wallet.
- Corporate customers can receive periodic invoices based on actual usage.
- Marketing-message costs can be charged to the relevant campaign budget.
- Premium customers can receive dedicated tariffs or policies.
- Certain notifications can first be delivered through Push Notification, with SMS used only as a fallback.
- Low-value transaction alerts can follow a different policy from sensitive or high-value transactions.
Under this model, the bank is no longer simply a sender of messages; it becomes the owner of its own notification policy.
A Wallet That Is More Than a Wallet
The name Notification Wallet may initially suggest a simple mechanism for charging and deducting messaging costs. In practice, however, Arad’s product goes far beyond a conventional SMS wallet.
The platform sits between notification-generating banking systems and the delivery infrastructure. Core Banking, card systems, lending platforms, cheque systems, fraud-management systems, internet banking, mobile banking, CRM, and other applications submit events to Notification Wallet instead of sending messages directly.
At that moment, the platform makes a series of decisions:
Which system generated the request? Is the sender authorized? Which customer and account does the message belong to? What is the bank’s policy for this event? Is the notification service enabled for this account? Does the customer have an active package or sufficient balance? Should the cost be funded by the customer, the bank, a prepaid package, postpaid credit, or a campaign budget? Is SMS the appropriate channel, or should Push Notification be used instead? And ultimately, should this message be allowed into the delivery pipeline at all?
Only after these questions have been resolved is the approved notification handed over to the messaging infrastructure.
This separation produces an important architectural benefit: the delivery infrastructure is responsible for delivering the message, while Notification Wallet is responsible for determining why it should be sent, whether it is permitted, and how it should be funded.
As a result, a bank can introduce an independent layer of notification governance without replacing its existing SMS Gateway or messaging infrastructure.
Managing Notifications at the Account Level, Not Just by Mobile Number
One of Arad Notification Wallet’s key differentiators is its concept of a flexible profile.
A mobile number alone is not always sufficient for managing banking services. One customer may have several personal, corporate, joint, or loan-related accounts and may want different notification services for each. A bank may also wish to apply different financial models depending on the account, customer segment, or banking relationship.
Arad Notification Wallet can create profiles based on mobile number, customer number, account number, national identification number, or a combination of these identifiers.
As a result, the same customer may have an active notification package for a current account, postpaid messaging for a corporate account, notifications disabled for another account, while still receiving essential security alerts regardless of balance.
For the bank, this enables more precise service delivery. For the customer, it means paying in accordance with actual needs.
From General Expense to a Measurable Revenue Model
A major reason banking-message costs appear difficult to control is that all consumption is typically grouped into a single cost pool. Notification Wallet breaks that pool down into measurable components.
Banks can design different packages for retail and corporate customers: a basic notification package, current-account package, business-account package, high-transaction package, combined SMS-and-Push package, or any other model aligned with the bank’s product strategy and customer experience.
Alongside packages, the platform supports prepaid wallets, postpaid billing, full bank sponsorship, campaign-budget charging, and hybrid payment models.
The economic value of this capability is not simply about shifting costs from the bank to the customer. Carelessly transferring charges can cause dissatisfaction and damage the customer experience.
The real value lies in allowing the bank to distinguish among critical messages, basic services, optional services, and value-added services, and to make an informed financial decision for each.
Messaging can therefore evolve from an undifferentiated overhead expense into a portfolio of services that can be designed, measured, and priced.
Every Rial and Every Message Can Be Traced
Any platform that makes decisions about credit, packages, and financial consumption must support precise auditing. For this reason, a financial Ledger sits at the core of Arad Notification Wallet.
Before a message is sent, the required amount or usage unit is first reserved. If the message is accepted into the delivery process, that reservation is converted into confirmed consumption. If the message fails before final acceptance, the reserved credit is released.
Top-ups, reservations, consumption, releases, refunds, corrections, and postpaid usage are all recorded independently.
The bank can therefore trace the complete lifecycle of every message from beginning to end.
When was the request generated by the banking system? What decision did Notification Wallet make? From which source was the cost reserved? To which gateway was the message delivered? What was the final delivery status? And how was its financial outcome recorded?
The platform also enables reconciliation across three primary records: the banking system request, the Notification Wallet financial record, and the delivery-infrastructure report. Any inconsistency between these three layers can be identified and investigated.
For finance, audit, IT, and digital-banking teams, this means eliminating the gap between a reported message count and the verifiable reality of each individual message.
Security at the Level of a Banking Financial Decision
Notification Wallet does not merely process message content; it also determines whether a message is authorized and how its cost should be funded. Its security model therefore cannot be limited to that of a simple messaging web service.
For banking environments, the platform can support certificate-based secure communication, request signing, dedicated identities for each source system, authorized-address controls, and access restrictions based on event type, delivery channel, and message pattern.
For example, a card system may be permitted to generate only approved card-related events, while a lending platform may have access only to installment-related notifications.
Every request is also assigned a unique identifier so that, in the event of a timeout or retransmission by the source banking system, neither the message nor its financial charge is duplicated.
At banking scale, this is not an optional feature. Preventing duplicate messages, double charging, and fraudulent requests is an integral part of financial service integrity.
Without Replacing the Bank’s Existing Infrastructure
One of the major barriers to transformation in banking is the assumption that existing systems must be completely replaced. Arad Notification Wallet was not designed around such an approach.
The product does not replace Core Banking or the SMS Gateway, and banks do not need to abandon their existing delivery infrastructure to use it.
Notification Wallet is deployed as an independent layer before the gateway and can connect to the bank’s existing infrastructure, Arad Messaging Platform, Arad Omni Switch, or other messaging gateways.
The platform can be deployed within the bank’s own data center and has been designed with multi-organization architecture, segregated access control, audit reporting, and connectivity to internal banking systems.
Deployment can also be phased. A bank may begin with a limited group of events or customers, then expand to high-transaction accounts and corporate clients, and finally extend the solution across all notification services.
In this way, the economic and operational value of the platform can be measured within a controlled scope before full-scale rollout.
The Question Banks Should Be Asking Now
The question banking executives should ask today is not simply:
“How can we send SMS more cheaply?”
The more important question is:
Why should every message, for every customer, every account, and every event, follow the same financial logic and the same communication channel?
Arad Notification Wallet is designed to answer this question.
It does not hide messaging costs, nor does it merely redirect delivery traffic. Instead, it returns the decision-making logic to the bank.
With this platform, a bank can know what was sent, why it was sent, to whom it was sent, who paid for it, and whether a better delivery option was available.
At a time when the cost of customer communication continues to rise, a bank’s competitive advantage does not lie simply in sending more messages. It lies in ensuring that every message is sent intentionally, measurably, and in proportion to the value it delivers.
Arad Notification Wallet provides the infrastructure for exactly this transformation: turning banking notifications from an unavoidable and opaque expense into a transparent, policy-driven, multichannel, and potentially revenue-generating service.
Banks have been paying for messages for years. Now it is time for them to take control of how those messages are managed.