As instant payments mature, financial institutions need to look beyond network participation and consider how send capabilities can support real payment use cases, transaction activity and deeper account-holder relationships.
Much of the early conversation around instant payments focused on connectivity. For banks and credit unions, being able to receive a FedNow or RTP transaction represented an important first step: the institution became reachable on a real-time network, funds could arrive immediately and account holders could participate when another party initiated the payment.
Receive remains an important capability, but it is only one side of the transaction. As instant payments become a more established part of the payments environment, the strategic discussion is increasingly shifting toward what financial institutions can do once they are able to originate transactions themselves.
Send changes the role of instant payments inside the institution. Instead of simply accepting an incoming payment, a bank or credit union can incorporate real-time money movement into products, commercial services and digital experiences. That creates opportunities to generate transaction activity, address specific account-holder needs and keep more of the payments relationship within the institution.
Send turns connectivity into a usable payment capability
The distinction becomes clearer when viewed through actual use cases. A financial institution with send capability can support account-to-account transfers, business disbursements, supplier payments, loan proceeds and other transactions where immediate availability has practical value. Those are not simply faster versions of existing payments; in many cases, speed changes when and how the payment can be used.
For commercial customers, the ability to send funds immediately can improve the timing of supplier payments, disbursements and other operating transactions. Consumers may value immediate movement between accounts or access to funds at the moment they are needed. The specific opportunities will differ by institution and customer base, but they begin with the ability to originate the transaction.
This is why receive should be viewed as a foundation rather than the final stage of an instant paymentsstrategy. Reachability gives the institution access to the network. Send gives product, payments and digital teams something they can incorporate into services that account holders actively choose to use.
Transaction activity matters more than technical availability
That progression from connectivity to usage is also visible in the Federal Reserve’s 2027 FedNow Discount Program. Qualifying institutions can receive statement credits for both receive and send capabilities, but the potential send incentives are considerably larger and are tied to actual transaction volume.
Receive discounts can reach $20,000 depending on an institution’s FedACH Receipt Discount Program status and other requirements. Send discounts can reach $80,000 for qualifying institutions, with volume thresholds that vary based on FedACH status. Existing FedNow senders can also qualify through growth in average monthly send volume when the applicable requirements are met.
The structure is notable because it places emphasis on what happens after an institution connects. For send, technical enablement alone is not enough to earn the full incentive. The institution has to generate transactions.
That makes adoption part of the implementation discussion. A bank or credit union considering send should be identifying likely users and use cases while the technology is being deployed, not after it is complete. If the goal is meaningful transaction volume, the product strategy, operational model and account-holder experience have to develop alongside the connection to the rail.
Keeping the payment relationship inside the institution
There is also a broader relationship issue at stake. Consumers and businesses already have ways to move money quickly, but those experiences are often provided by fintech companies that sit between the accountholder and the financial institution. When the institution cannot offer a comparable capability directly, part of the payment experience moves outside its own environment.
Instant-payment send capabilities give banks and credit unions an opportunity to bring more of that activity back into their own digital channels. The account holder can initiate the payment through the institution with which the deposit relationship already exists rather than moving funds into an outside holding account or relying on another provider to complete the experience.
Pidgin’s model is designed around that principle. The platform connects the financial institution’s existing core, digital banking environment and third-party applications to FedNow, RTP and other faster payment options while allowing the institution to remain at the center of the transaction. The objective is not simply to make an instant payment technically possible, but to help the bank or credit union offer the capability as part of its own account-holder relationship.
That can have implications beyond convenience. Keeping payment activity within the institution can provide better visibility into account activity, support deposit relationships and create additional opportunities to develop services around the way consumers and businesses actually move money.
Send creates more room for product and revenue strategy
As transaction activity grows, send also gives institutions more options for thinking about how instant payments fit into the business. Not every instant payment needs to carry a fee, and the value of the capability should not be measured only by transaction revenue. In some cases, the return may come through a stronger commercial relationship, improved deposit retention, a more competitive digital experience or the ability to offer a service that would otherwise occur outside the institution.
Other use cases may support direct revenue opportunities. Commercial customers, for example, may be willing to pay for payment services that solve a meaningful timing or operational problem. The appropriate model will depend on the institution, its market and the value of the use case.
What matters is that send gives the institution choices that receive alone does not. Once the bank or credit union can originate real-time transactions, instant payments can become part of product design and relationship strategy rather than remaining primarily a network-access capability.
The next phase of instant payments is about what institutions do with the rails
Pidgin can enable financial institutions to receive and send payments across FedNow and RTP today, but the technology connection is only the beginning of the work. Institutions still need to determine where real-time payments solve an actual problem, how the capability should appear within existing digital experiences and which account-holder segments are most likely to use it.
The 2027 FedNow incentives can help offset some of the cost of moving forward, particularly for institutions that qualify for the higher send discounts. Their greater significance, however, is that they reinforce a broader direction in instant payments: participation is increasingly being measured not simply by whether an institution is connected, but by whether the capability is being used.
For institutions that began with receive, that creates a natural next question. The issue is no longer only whether the bank or credit union can accept an instant payment. It is whether the institution can originate one when an account holder needs it and build services around that capability.
Receive establishes reachability. A more mature instant payments strategy considers what happens next: which transactions the institution wants to originate, how those transactions support its account-holder relationships and how send can become part of the broader payments business.