A parent pays S$200 for an online course. The card issuer approves the purchase in seconds, but the merchant receives money later, after clearing, settlement and the acquiring bank’s own payment process. The card network connects the institutions, but is not automatically the lender, seller or bank holding every customer’s money. If a message fails or a duplicate charge appears, knowing who owns each stage is essential.
Payment card network services operate common rules and infrastructure for card authorisation, clearing, interbank settlement and related corrections. Their gold standard is reliable exchange of approved messages, secure network access, accurate institutional financial records, transparent payment-system costs and an orderly path for reversals, refunds and disputes.
The network’s role is distinct from Credit Card Issuing, Merchant Acquiring and Payment Gateway Services. This extends the eduKate Gold Standard management hub.
Worked merchant fee: S$200 purchase, multiple economic roles
At a hypothetical 2.5% merchant discount, a S$200 sale has **S$5** in merchant-facing charges, leaving S$195 before other items. An invented 1.8% interchange component would equal S$3.60. The remaining S$1.40 could include acquiring, network and processing costs; it cannot accurately be called one party’s universal fee. This is not a current tariff.
Sixteen payment card network chapters
1. The network connects parties with distinct legal roles
In a common card-payment model, the issuer maintains the cardholder relationship, the acquirer serves the merchant, and the card network provides standards and message exchange between participating financial institutions. Payment facilitators or processors can act under additional approved arrangements.
The VisaNet Connect documentation describes routing an acquirer’s authorisation request to an issuer and returning that issuer’s decision. The network is not inherently the merchant’s bank and does not make the seller’s goods genuine. A sound service identifies exactly which institution handles each legal and operational consequence.
2. Authorisation is not the same as money finally settled
An approved card request may reserve funds or confirm issuer authorisation, but the merchant may still need to submit a capture for clearing. Later, the network and its financial participants process settlement. A customer can see a pending hold before the corresponding merchant deposit exists.
Keep the original transaction reference across authorisation, capture, clearing, refund and settlement records. Visa’s acceptance interface distinguishes authorisation and capture. Never label the merchant paid merely because the checkout displayed an approval code.
3. Network access needs authentic participants
A payment gateway or technology partner may use network facilities through a sponsoring acquirer. Not every company can directly act as an issuer, acquirer or network participant merely because it has an API key. Contracts, technical certification and operating standards determine available services.
Visa’s developer documentation explains production access and approval requirements for particular interfaces. Maintain accurate registration, legal identity, permitted messages and sponsoring institution information. One fraudulent or compromised participant can affect many customers, so the network must know who sent each material instruction.
4. Understand authorisation response codes and timeouts
An issuer can approve, refuse, or require supported additional verification. A transport failure may result in no response while the issuing system still processed the request. Repeating the entire payment without checking the original reference can cause multiple holds or charges.
Preserve message IDs, timestamps, issuer responses and technical errors separately. An acquirer should know which transactions are pending and when an approved void or reversal is available. A bank’s genuine refusal is not the same status as an inaccessible network endpoint, and the customer-facing checkout should respect that distinction.
5. Different payment channels have different security evidence
In-store chip transactions, contactless mobile tokens and e-commerce purchases may carry different authentication or cryptographic information. The card network can support relevant verification functions while the issuer makes its own decision using permitted security data.
The VisaNet Issuing interface describes issuer-side authorisation and related checks. Networks should govern acceptable message types and the safe handling of payment credentials. The existence of a token is not proof that the customer agreed to every future merchant charge.
6. Captures, sales, refunds and voids are not interchangeable
An immediately fulfilled purchase may follow one permitted path while an authorised but delayed shipment requires capture later. A merchant refund after settlement differs from voiding an authorisation not yet fully completed. Mixing these messages can make customer balances and merchant accounting inconsistent.
Document when each message is available under the actual scheme, how it relates to the original sale and which party must authorise it. A service provider should not process a new charge merely to repair a missing capture acknowledgement. Reconstruct the original attempt before retrying.
7. Interchange is not simply a network charge paid by the merchant
Interchange reimbursement fees generally represent transfers between the card issuing and acquiring institutions under scheme rules. The merchant pays a contracted merchant service or discount fee to its acquirer, which can reflect interchange, network assessments, processing and other commercial services.
The Visa fee information and Mastercard merchant interchange guide explain this distinction. Networks should make current fee rules available to participants without claiming that every merchant faces one universal rate.
8. A worked merchant service fee must show real cost categories
Suppose a fictional S$200 transaction has a 2.5% merchant discount charge, or S$5. The merchant receives S$195 before any other deductions. If a hypothetical underlying interchange component equals 1.8%, that portion would be S$3.60; the residual S$1.40 could include several acquiring, processing or scheme cost components.
Do not call the entire S$5 a network fee or claim the remaining S$1.40 is paid solely to Visa or Mastercard. Rates depend on country, card type, processing conditions, acquiring agreement and applicable rules. The example is arithmetic only, not a Singapore payment-network fee quote.
9. Clearing records and net interbank settlement require reconciliation
Card-network clearing may combine large numbers of accepted financial messages into settlement obligations between issuing and acquiring institutions. Net positions can be correct at the participant level while one merchant’s payout report contains a missing or duplicated fee entry.
Preserve the link from individual accepted clearing records to participant totals, adjustments and bank settlement confirmations. VisaNet documentation describes daily clearing and settlement reports. Investigate mismatches rather than hiding them in suspense accounts. A correct net interbank payment does not automatically prove that every acquiring merchant was paid the correct amount.
10. Cross-border payments have extra currency and timing layers
A consumer can buy in one currency while an issuer bills in another and an acquirer settles through yet another permitted arrangement. Currency conversion timing, local regulations and processing fees can all affect the final amounts. A network provides routes and rules, but not necessarily every cardholder exchange rate.
Record purchase currency, authorisation, clearing conversion where relevant, final cardholder billing and acquirer settlement. Label any estimated conversion as estimated. An appealing exchange-rate display should not be represented as the final amount on every issuer’s statement if the applicable product uses a different processing basis.
11. Dispute management connects banks rather than replacing their roles
The issuer normally receives a cardholder’s concern, and the acquirer handles the merchant’s response under the scheme. The network’s dispute rules can specify codes, evidence requirements and deadlines. The existence of those procedures does not mean every alleged fraud was genuine or every merchant defence succeeds.
Link the original transaction, claims stage, provisional monetary entries, representment and final outcome. Our Chargeback Management article examines the specific case handling. The network should make sure participating institutions can exchange correct evidence and settle lawful financial adjustments.
12. Refund and reversal messages must not manufacture duplicate payments
A merchant may request a refund while the issuing bank also investigates a cardholder chargeback. If the merchant and acquirer fail to match those events, the customer could receive duplicate credits while the business loses more than the original purchase. Repeated authorisation reversals can create other errors.
Preserve original payment references across corrections and keep final monetary outcomes visible. One network response saying a refund was accepted is not proof the cardholder’s account has already received the credited amount. Review overlapping cases before sending another payment.
13. Network cybersecurity includes participants and API access
A card network may be technically healthy while an approved processor’s credentials are compromised. Transaction-routing security therefore depends on participant certification, correct authentication, secure messages and change controls across systems. Artificially high approval rates do not demonstrate safe service.
Review access, credential rotation, permitted API functions and abnormal message volumes. Apply incident control and communications to affected participants. Preventing unauthorised network submissions is a shared operational process and should be tested under realistic merchant and processor incidents.
14. Recovering the network means reconciling incomplete transactions
During an outage, authorisations can time out, clearing messages may queue and settlement reports can arrive late. Restarting an API is not equivalent to establishing which transactions were accepted, reversed or completed financially. A rushed replay of queued messages can duplicate purchases.
Maintain durable message identifiers, controlled replay and authoritative participant reconciliation. Give clients a truthful account of affected functions and permitted customer actions. The incident closes only when the necessary transaction histories and settlement records agree and unresolved cases have actual owners.
15. Keep card rules current in each relevant jurisdiction
Card scheme rules differ by region, merchant category, product, payment type and date. Interchange rates, card acceptance and surcharging provisions can change. A table copied from an old market’s rules cannot be applied automatically to a current Singapore purchase.
Visa maintains a current rules and fees portal; Mastercard also publishes merchant fee resources. The network and each participant need dated rulebooks and procedures for communicating updates. A proposed rule should not be described as already in effect before its actual operative date.
16. The gold standard is a transaction trail every participant can trust
A network can send millions of messages per day, yet one customer still cares whether the purchase was charged once and one merchant whether funds arrived after the proper deductions. High throughput and low latency are important but incomplete measures of quality.
Audit authorisation accuracy, clearing integrity, settlement breaks, participant access, fee transparency, refunds, disputed transactions and outages. The gold standard is a safe, rules-based card infrastructure in which each participant can verify what happened and correct material errors without inventing new financial obligations.
Cardholder and merchant FAQs
Does authorisation prove the merchant received cash?
No. Authorisation, clearing, interbank settlement and merchant funding are different stages.
Does the card scheme always issue the customer’s credit?
No. A separate issuer generally maintains the cardholder account.
Is interchange the merchant’s full payment processing fee?
No. It is generally an interbank component while the merchant pays its acquirer under a separate pricing arrangement.
Are card chargebacks decided entirely by the network?
The issuer, acquirer and permitted network procedures each have specific roles.
Can a network outage cause duplicate authorisations?
Poor retries can produce duplicate or uncertain states; original references must be reconciled.
Card network control review
- Identify issuer, acquirer, network and approved technical partners.
- Keep authorisation, capture, clearing, settlement and merchant funding distinct.
- Prevent repeated messages from creating duplicate charges.
- Disclose interchange, network charges and merchant discount accurately.
- Track refunds and chargebacks against original transaction references.
- Apply current scheme rules and region-specific conditions.
- Test incident recovery through actual financial reconciliation.
Primary payment-network references and related eduKate articles
- Visa: VisaNet Connect Acceptance, Authorisation to Settlement.
- Visa: Issuer Payment APIs and Settlement Reports.
- Visa: Interchange, Network Rules and Merchant Pricing Distinctions.
- Mastercard: Interchange Fee and Merchant Discount Explanation.
- eduKate: Merchant Acquiring.
- eduKate: Credit Card Issuing.
- eduKate: Chargeback Management.
Educational payment-network operations, not current payment tariffs or legal instructions. Participant arrangements, regional rules and bank processes determine actual outcomes.