How Money Actually Moves on Card Rails

Someone taps their card to pay for a coffee. There’s a quick beep, the transaction is approved, and they walk away. It feels instant.

A lot has to happen behind the scenes in those couple of seconds - the transaction is checked against a set of rules and returns a decision. The actual movement of money, however, only comes later, usually a day or two after the purchase.

Most consumers don’t need to think about any of this. But if you’re running a card program, these mechanics shape how everything works. They explain why refunds take time, how costs are structured, and what “instant” really means in practice.

In this blog, we walk through how a card transaction actually moves, who’s involved, and what happens at each step, so you can make better decisions about your program and avoid surprises when things don’t behave the way people expect.

The Five Players in Every Card Transaction

Every card transaction involves a small group of players working together behind the scenes. Each one has a specific role, and understanding who does what makes the rest of the process much easier to follow.

• Cardholder: The person or entity making the payment. This could be someone tapping their card in a store, paying online, or using a prepaid card issued as part of a rewards or payroll program.
• Merchant: The business accepting the payment. This can be anything from a coffee shop to an online retailer or a service provider.
• Acquirer: The merchant’s bank or processor. This is the party that processes card payments on behalf of the merchant. It collects the transaction details and routes them into the card network.
• Card Network: Networks like Visa, Mastercard, American Express, and Discover Financial Services. They act as the central routing layer and move transaction messages between parties, and set the rules that everyone in the system follows.
• Issuer: The cardholder’s bank or program. This is the entity that issued the card and controls the funds behind it. They ultimately approve or decline the transaction based on available funds, fraud checks, and program rules. This is where Berkeley and its bank partners sit.

The card network doesn’t actually move money or hold funds. Its role is to move information. The money itself moves later, through a two-phase process. 

The Two Phases: Authorization and Clearing & Settlement

Every card transaction happens in two distinct phases. The first is what happens immediately at the point of payment, and the second happens later, after the customer has already walked (or clicked) away.

Phase 1: Authorization

Here’s what happens in those couple of seconds before the terminal beeps:

• The merchant’s terminal sends the transaction details to the acquirer.
• The acquirer passes it through the network to the issuer.
• The issuer checks a few things very quickly such as: Is the card valid? Are there enough funds or available credit? Does the transaction pass fraud checks and any program rules that are in place?
• The issuer sends back an approval or a decline.

If it’s approved, the amount is held. The cardholder sees a pending charge, and the merchant gets confirmation that the payment can go through.

At this point, no money has changed hands.

Phase 2: Clearing and Settlement

This part happens later, usually in batches at the end of the day:

• The merchant groups together the day’s transactions and sends them to the acquirer.
• The network matches each one back to its original authorization.
• The issuer moves the funds through the network’s settlement process.
• The acquirer receives the funds and pays the merchant.

It’s only here where money leaves one account and lands in another. 

Instant Approval vs. Instant Money Movement

It’s very important to distinguish between the concept of instant approval and instant money movement as this can get confusing when it comes to customer expectations. 

A payment can be approved right away, but the merchant won’t actually receive the funds until later. Instant money movement implies that money has actually changed hands right away - while that distinction doesn’t matter much when a purchase is made, it can get tricky if the customer wants a refund. 

It’s easy to assume that an approved payment can simply be reversed. In practice, what happens next depends on where exactly the transaction lies between authorization and settlement.

• Refunds: A refund isn’t a reversal of the original transaction. It’s a completely new transaction going back the other way. It has to go through its own clearing and settlement process, which is why refunds can take time to show up.
• Disputes and Chargebacks: A transaction can’t be disputed while it’s still pending. Disputes and chargebacks only start after the transaction has cleared, and from there they follow network timelines that can take weeks to resolve.
• Voids vs. Refunds: If a transaction is caught early enough, usually on the same day, it can be voided. That cancels the authorization and the hold drops off. Once the transaction has cleared, that option is gone, and the only way to return funds is through a refund.

If your program promises “instant payments,” you need to be clear about which half of the process that refers to. Authorizations are generally instant, but the actual movement of money is not.

The Money Path: Who Gets Paid and How

Once a transaction moves into clearing and settlement, the money starts to flow between the different parties involved. It’s not always obvious how that works, and it often surprises people how many hands are involved along the way.

Take a simple example - a person uses a card for a $50 purchase, whether online or in person.

The merchant doesn’t receive the full $50. Instead, they receive that amount minus a fee, usually referred to as the merchant discount rate. This typically falls somewhere in the range of 1.5% to 3.5%, depending on the type of card and the setup behind it.

That fee is then split between a few different parties:

• Interchange: This is the largest portion of the fee. It’s paid by the acquirer to the issuer and is set by the card networks. If you’re on the issuing side, this is the part that flows back to your program.
• Network Fees: The card networks take a small fee for routing the transaction and maintaining the infrastructure.
• Acquirer Markup: The acquirer or processor keeps a portion for handling the merchant side of the transaction.

If you’re a merchant, these fees are simply a cost of accepting cards. But if you’re issuing cards, interchange becomes a source of revenue. That’s one of the reasons prepaid and debit programs can work at scale. As card usage grows, so does the revenue tied to that activity, which starts to change how you think about the economics of a card program and where the value actually sits.

What It Means to Be the Issuer

If you’re issuing a card, either directly or through a partner, you’re the one behind every transaction. That role carries a set of responsibilities that tend to become visible only once a program is live.

• You’re responsible for every approval decision: In those couple of seconds when a transaction is sent through, your systems are making the call. The rules you’ve set, whether around balances, spend controls, or fraud, are applied in real time. If something isn’t working as it should, transactions fail and cardholders feel it immediately.
• You need to be able to fund settlement: Once transactions move beyond authorization, the funds have to be there. This means thinking about how the program is funded and making sure it can support ongoing usage, not just initial issuance.
• You are in the middle of the compliance chain: The issuer is responsible for meeting regulatory and network requirements. That includes KYC, AML, and ongoing fraud monitoring, which are all ongoing processes. 
• You’re tied directly to the economics of the program: Interchange flows to the issuer, which is where there is revenue opportunity. At the same time, how the program is structured will determine whether that revenue just offsets costs or becomes profitable.
• You manage what happens when things go wrong: Disputes and chargebacks fall to the issuer. When a cardholder raises an issue, it’s your process that determines how it’s handled and how long it takes.

Launching a card program is a bigger undertaking than it may seem. The easy part is choosing a card design, but the more complicated part includes managing the entire system with its own rules, timing, and responsibilities. How well that’s set up has a direct impact on how the program performs.

The Infrastructure Most Companies Don’t Want to Build

Once you look at what sits behind issuing, it becomes clear why most companies don’t try to do it on their own.

Becoming a direct issuer means putting a lot of pieces in place, including:

• Network membership: Getting direct access to card networks, along with meeting their technical, operational, and compliance requirements.
• A sponsoring bank relationship: Finding a regulated bank to support the program and hold the underlying funds.
• A processing platform: Building the system that handles transaction routing, authorization logic, and real-time decisioning.
• Compliance, fraud, and dispute operations: Conducting ongoing processes to manage KYC, AML, fraud monitoring, and chargebacks.
• Reconciliation and settlement infrastructure: Putting in place the systems that track transactions, move funds, and ensure everything balances correctly.
• Cardholder-facing tools: Developing and supporting the apps, portals, and statements that allow users to access and manage their accounts.

Each of these comes with its own setup, cost, and ongoing operational overhead. Bringing them together into something that works reliably can take years and significant investment before a single card is even in a customer’s hand.

As payments become more embedded into products and day-to-day experiences, more companies are looking to offer card-based programs. But for organizations where this isn’t their core business, building and running that entire infrastructure doesn’t make sense. The goal is usually to deliver the functionality, not to take on the complexity and cost that sits behind it.

That’s where the platform model comes in. Instead of building the entire issuing stack from scratch, companies work with partners who already sit inside the network and bank ecosystem. The infrastructure, compliance, and settlement layers are handled behind the scenes, while the business focuses on the program and the customer experience.

Why Understanding the Rails Matters

When you understand how the rails work, it becomes much easier to make informed decisions about how your program is set up and who you work with.

It helps you to:

• Ask better questions when evaluating providers, because you understand how transactions actually move and where things can break down
• Set realistic expectations internally, especially around what “instant” does and doesn’t mean in practice
• Design your program more effectively, including how you take advantage of interchange economics
• Decide what to own and what to delegate, based on what sits behind the issuing, settlement, and compliance layers

If you’re exploring how a card program could work for your organization, working with a partner like Berkeley Payment Solutions means more than just having the rails in place. It means working with a provider that already brings together the issuing, banking relationships, processing, and compliance infrastructure into a single, reliable setup.

That allows you to focus on building a program that delivers value, rather than managing the systems and operations behind it.

‍