Payment Processing — How Money Moves from Customer to Business

How payment processing moves money

The payment processing flow moves a customer’s money to a business through secure checks and bank messages. It starts when a customer pays and ends when the business receives its funds. Several firms and banks pass data along the way. The money does not usually move in one instant.

For example, a customer buys a $40 item online with a card. The store sends the payment details to a gateway. The gateway routes them through a processor and card network to the customer’s bank. The bank approves or declines the request. If approved, funds are later sent to the merchant’s account.

Two steps matter most to merchants: approval and settlement. Approval checks whether the payment can proceed. Settlement moves the funds after approval. A customer may see an approved payment before the business can use the money.

Why the flow matters

Knowing each stage helps a business spot delays, compare provider fees, and fix failed payments. It also helps staff explain pending charges to customers. The flow is similar for in-store and online sales, though the device and security checks may differ.

Key parts of a payment processing system

Each part has a distinct job. A small store may buy several services from one provider, while a larger firm may choose separate vendors. The names can overlap, so ask each provider who handles routing, approval requests, and settlement.

• Customer: Chooses a payment method and gives the details needed to pay.
• Merchant: The business that sells goods or services and accepts the payment.
• Payment method: A card, bank transfer, digital wallet, or local payment option.
• Point-of-sale system: In a shop, the terminal or till that takes payment details.
• Payment gateway: Securely sends payment details from a website or device to the payment provider.
• Payment processor: Routes payment messages between the merchant, banks, and card network.
• Card network: Sends messages between the cardholder’s bank and the merchant’s bank.
• Issuing and acquiring banks: The issuer serves the customer’s card; the acquirer serves the merchant.

These roles can be bundled. A payment service provider may offer a gateway, processing, and merchant account services together. The merchant still needs to know which firm holds funds and who handles disputes.

Steps in a typical payment flow

1. Initiation: The customer taps, inserts, or enters payment details at checkout.
2. Encryption: The checkout device protects sensitive details before sending them onward.
3. Routing: The gateway or processor sends the request through the right network to the customer’s bank.
4. Authorization: The bank checks the account, available funds, and risk signals. It returns approval or decline.
5. Capture: The merchant confirms the approved amount for payment. Some businesses capture it right away; others wait until shipping.
6. Settlement: Banks and payment firms work out the amounts due. The acquirer then pays the merchant, minus fees.

An approval is not the same as money in the merchant’s account. For example, a hotel may approve a card at check-in, then capture the final bill at checkout. The customer’s bank may show a pending hold before the final amount posts.

Timing depends on the payment method, provider, bank, and business schedule. Card funds often arrive after one or more business days, but terms vary. Check the provider agreement for cut-off times, payout days, and reserve rules.

A payment processing flow chart in plain text

This payment processing system flow chart shows the main route. It keeps the key choices visible without hiding the work behind each handoff.

1. Customer starts payment at a website or terminal.
2. Gateway protects the details and sends a request to the processor.
3. Processor routes the request through the card network.
4. Customer’s bank approves or declines the payment.
5. Response travels back to the merchant and customer.
6. Merchant captures approved funds, then settlement sends the payout.

A decline ends the payment attempt, though the customer can try another method. An approval lets the sale proceed, but later steps still matter. Refunds and disputes follow separate paths and may take several days to appear.

Businesses can use this flow chart to ask where a failed payment stopped. A gateway log may show a message was sent, while the processor may show a bank decline. Knowing the handoff narrows the issue quickly.

What payment processing costs include

Payment costs vary by provider, payment method, card type, sales volume, and risk. A common pricing model combines a percentage with a fixed amount per payment. For a $40 sale, a sample fee of 2.9% plus $0.30 would equal $1.46. This example is not a market quote.

Common charges include the provider’s processing fee, interchange fees set for card payments, and network fees. Some providers also charge monthly, cross-border, currency conversion, refund, or dispute fees. A low headline rate can cost more if extra charges apply.

Compare providers using your own sales mix. Review average sale size, card-present versus online sales, foreign cards, refund rates, and payout timing. Ask for a sample statement and a written list of fees. Check whether fees apply to refunds or failed payments.

Best practices for safer, smoother payments

Make checkout clear and keep it short. Show accepted payment methods before the final step, state the full price, and give customers a clear error message when payment fails. Offer a backup method without asking customers to enter the same details repeatedly.

Reduce fraud risk with tools that match the sale. Use address or security checks where they fit, and review unusual orders before shipping. Too many checks can block good customers, so track both fraud losses and genuine payment declines.

Keep card data out of your own systems when possible. Choose trusted providers and follow their security steps. The PCI Security Standards Council’s PCI DSS overview explains the baseline rules for protecting card data. Ask your provider which tasks remain your responsibility.

Finally, test the full journey on a phone and in person. Check approval messages, receipts, refunds, and payout reports. Review declines and fees each month. Small fixes can improve the customer payment experience while making costs easier to manage.