What import mechanics are and why banks use them
Import mechanics are the technical and procedural systems that payment networks — Visa, Mastercard, American Express, and others — use to move transaction data and funds between the banks and card issuers involved in a purchase. When you swipe a card at a store, the merchant's bank receives the transaction details, and those details must be routed to your card issuer's bank through the network. Import mechanics are the rules and infrastructure that govern how that routing happens, what information travels with it, and when settlement occurs.
Banks and card issuers rely on import mechanics because they standardize the process. Without them, every bank would have to negotiate separate data-sharing and fund-transfer agreements with every other bank. Instead, the payment network acts as the intermediary, accepting transaction files in a standard format from acquiring banks (the merchant's bank) and delivering them to issuing banks (your bank) in a format those banks can process automatically.
Understanding import mechanics matters to consumers because they affect how quickly transactions post to your account, whether a charge appears as pending or settled, and how disputes are handled. They also determine what information your bank receives about a transaction and when that information arrives — which can affect fraud detection, spending limits, and whether a transaction is approved or declined in real time.
Key Takeaways
- Import mechanics are the standardized processes that payment networks use to send transaction data from a merchant's bank to your card issuer's bank.
- Transaction files move through the network in batches at set times each day, not in real time, which is why a purchase may show as pending before it settles.
- The acquiring bank (merchant's bank) formats transaction data according to network rules and sends it to the payment network, which then routes it to your issuing bank.
- Settlement — when money actually moves from your account to the merchant's account — typically occurs one to three business days after the transaction is authorized.
- Import mechanics determine what dispute information is available if you contest a charge, because the data captured during import is what both banks use to investigate.
The three stages: authorization, clearing, and settlement
A payment transaction moves through three distinct phases, each governed by different import mechanics. Authorization happens in real time (or near-real time) when you present your card. The merchant's point-of-sale system sends your card number, amount, and merchant details to the acquiring bank, which queries your card issuer to confirm the card is valid and you have sufficient funds or credit. Your issuer responds with an approval code or decline, and the merchant sees the result within seconds.
Clearing begins after authorization and involves the actual movement of transaction data through the payment network. The acquiring bank collects all authorized transactions from a business day into a batch file, formats that file according to the payment network's import specifications, and sends it to the network. The network then routes these batches to the appropriate issuing banks. This stage typically happens overnight or in scheduled windows throughout the day, not continuously.
Settlement is when money moves. After an issuing bank receives and processes a cleared transaction, it debits your account and the acquiring bank credits the merchant's account. The payment network coordinates this fund transfer through the banking system's automated clearing house (ACH) or wire network. Settlement usually takes one to three business days after authorization, depending on the network's rules and the banks involved.
How acquiring banks format and send transaction files
The acquiring bank — the merchant's bank — is responsible for preparing transaction data for import into the payment network. It must capture specific fields from each transaction: your card number (or a token representing it), the transaction amount, the merchant's ID, the authorization code, the date and time, and any additional data the network requires. Different networks have different field requirements and file formats, so an acquiring bank handling Visa, Mastercard, and American Express transactions must maintain separate import processes for each.
Most acquiring banks use one of two standard formats: ISO 8583 for real-time or near-real-time messages, and NACHA (National Automated Clearing House Association) or network-specific batch formats for end-of-day clearing files. ISO 8583 is an international standard that defines how transaction data is structured in a message; NACHA is the U.S. standard for ACH transactions and is often used for settlement instructions. Smaller merchants or those using third-party payment processors may not see these formats directly — the processor handles the formatting and submission on their behalf.
The acquiring bank must also validate the data before sending it. It checks that card numbers are in the correct format, amounts are reasonable, and merchant IDs are active. If validation fails, the transaction may be rejected before it ever reaches the payment network, and the merchant is notified. This is why a transaction can be authorized at the point of sale but never appear on your statement — it failed validation during the import process.
What happens when the payment network receives a transaction file
Once the acquiring bank submits a transaction file to the payment network, the network's systems receive, validate, and route it. The network checks that the file format is correct, that all required fields are present, and that the data is internally consistent. If the file has errors, the network may reject the entire batch or flag specific transactions for manual review. The acquiring bank receives a report indicating which transactions were accepted and which were rejected.
For transactions that pass validation, the network routes them to the issuing bank based on the card number. The card number's first six digits (the Bank Identification Number, or BIN) tell the network which bank issued the card, so the network knows where to send the transaction. The network may also explore its own rules at this stage — for example, checking whether the transaction amount exceeds limits set by the card issuer or whether the merchant category code matches restrictions the issuer has placed on the card.
The payment network also handles exceptions during import. If a transaction cannot be routed because the issuing bank is temporarily unavailable, the network queues it and retries. If a card number is invalid or the issuing bank cannot be identified, the network generates an exception report. The acquiring bank must then investigate and either resubmit the transaction with corrected data or report the failure to the merchant.
How issuing banks process imported transactions
When your card issuer receives a transaction file from the payment network, it performs its own validation and processing. The issuer checks that the cardholder (you) exists in its system, that the card is active and not reported lost or stolen, and that the transaction amount does not exceed any limits or restrictions on the account. The issuer also runs fraud detection rules — checking whether the transaction is consistent with your spending patterns, whether the merchant is in an unusual location, and whether multiple transactions are occurring in a short time window.
If the issuer identifies a potential problem, it may flag the transaction for manual review or decline it outright. If it approves, the issuer posts the transaction to your account. At this stage, the transaction typically appears as pending on your statement — it is recorded but not yet final. The pending status remains until settlement occurs, which is when the transaction becomes posted and the funds are actually debited from your account.
The issuer also stores the transaction data for later use. This data is what appears on your monthly statement, what you see in your online account, and what the issuer uses if you dispute the charge. If the transaction data is incomplete or unclear during import, the issuer may not have enough information to investigate a dispute later, which is why import mechanics directly affect your rights as a consumer.
Why import timing affects when transactions appear on your account
Transactions do not move through import mechanics continuously throughout the day. Instead, acquiring banks collect transactions into batches and submit them at scheduled times — typically once per day in the evening, though some banks submit multiple batches. The payment network processes these batches in windows, and issuing banks process them in their own windows. This batching is why a transaction authorized at 2 p.m. might not appear on your account until the next morning.
Weekends and holidays extend the timeline further. If you make a purchase on Friday evening, the acquiring bank may not submit the batch until Saturday morning, the network may not process it until Monday, and your issuer may not post it until Tuesday. This is why transactions often show as pending for two to three business days — the import process itself takes time, separate from the actual fund transfer.
Some merchants and payment processors use real-time import, which submits transactions to the network when ready rather than batching them. This is more common for high-value transactions, online purchases, and subscription services. Real-time import can reduce the pending period to hours rather than days, but it requires more sophisticated infrastructure and higher costs, so most small merchants do not use it.
How disputes and chargebacks use import data
If you dispute a charge, both your issuing bank and the acquiring bank rely on the transaction data that was imported through the payment network to investigate. Your issuer has the data it received during import; the acquiring bank has the data it submitted. If the data is incomplete — for example, if the merchant category code is missing or the authorization code is incorrect — the investigation becomes difficult and your issuer may have less leverage in the dispute process.
The payment network also maintains records of what was imported, and these records can be subpoenaed or requested during a chargeback dispute. If the acquiring bank claims it submitted correct data but the issuing bank received incomplete data, the network's records show what actually moved through the system. This is why import mechanics matter to your consumer protections — poor data quality during import can weaken your position in a dispute.
Chargebacks — formal disputes filed through the payment network — follow specific rules about what evidence must be presented, and that evidence comes from the imported transaction data. If you claim you never authorized a transaction, your issuer will look at the authorization code and the merchant details in the imported record. If you claim the merchant charged you twice, your issuer will look at whether two separate transactions with different authorization codes were imported. The import record is the foundation of the entire dispute process.
Frequently Asked Questions
Why does a transaction show as pending if it was already authorized?
Authorization and settlement are separate processes. Authorization confirms you have funds and the card is valid, but it does not move money. The transaction must then be imported through the payment network and processed by your issuer before settlement occurs. During this time, it shows as pending. Settlement typically takes one to three business days.
Can a transaction be authorized but never settle?
Yes. A transaction can be authorized at the point of sale but fail during the import process if the acquiring bank's data is invalid, the file format is incorrect, or the issuing bank rejects it during processing. In these cases, the authorization is reversed and the transaction never settles. You should not see a charge on your account, but it may take several days for the pending charge to disappear.
What information does the payment network capture during import?
The network captures your card number (or a token), the transaction amount, the merchant ID, the authorization code, the date and time, the merchant category code, and any additional fields required by the specific network. It does not capture your name, address, or phone number — those details stay between you and your issuer. The merchant does not receive your full card number after the transaction is authorized.
Why do some transactions settle faster than others?
Real-time import systems settle faster than batch systems. Subscription services and online merchants often use real-time import, which can settle within hours. Retail merchants typically use batch import, which settles in one to three days. Weekends and holidays also delay settlement because banks do not process batches on non-business days.
Can I see the import data for my transactions?
You can see the data your issuer received and processed — this is what appears on your statement and in your online account. You cannot directly see the raw import file or the data as it moved through the payment network. If you dispute a transaction, your issuer can request the full import record from the network, and that record may be provided to you as part of the dispute investigation.