TOEIC Link Payments and Card Networks Vocabulary: The Transaction-Lifecycle Cluster That Drives Reading Part 6 in the Card-Acquiring Vertical

Payments is one of the densest B2B verticals on TOEIC Link. Every Part 6 booklet seems to carry at least one email between a merchant and an acquirer, between a payment-service-provider account manager and a merchant operations team, or between a network's risk-and-compliance group and an issuing bank. The vocabulary that runs these passages is bounded by the transaction lifecycle — authorize, clear, settle, fund, reconcile, dispute — and once the lifecycle is internalized, the words follow.

This article is the focused TOEIC Link payments-and-card-networks vocabulary cluster, organized by transaction lifecycle stage rather than alphabetically because that is the structure ETS uses to construct items. The lifecycle runs from authorization through clearing through settlement through funding through reconciliation through chargeback and dispute resolution, and each stage carries its own dense collocation network.

Why payments-and-card-networks vocabulary matters on TOEIC Link

The payments register surfaces on TOEIC Link more often than most candidates expect, for three structural reasons.

Reason 1 — payments passages are operationally specific and self-contained. A two-paragraph email about a delayed batch settlement, a missed funding day, a chargeback representment window, or a card-network compliance update fits the Part 6 format perfectly. The operational specificity gives the passage tested anchor points without requiring background knowledge.

Reason 2 — the cluster is collocation-dense. A single payments email must reference authorization mechanics, settlement timing, fee schedules, and dispute deadlines. Each of those is a tight collocation set — authorize the transaction, capture the funds, settle the batch, fund the merchant account, representent the chargeback. ETS tests these as units, not as isolated words.

Reason 3 — payments vocabulary is cross-pollinated with other tested registers. Card-issuing vocabulary overlaps with the banking-and-investment cluster. Fraud-and-risk vocabulary overlaps with the cybersecurity-and-information-security cluster. Merchant-services vocabulary overlaps with the retail-and-ecommerce cluster. Mastering the payments cluster reinforces all three.

The transaction-lifecycle cluster, organized by stage

The cluster below is grouped by what the transaction is doing, not by part of speech. Memorize each group as a unit, with the collocations as the unit of memorization rather than the bare lemma.

Stage 1 — authorization and capture (≈26 words)

The cardholder presents the card. The merchant submits the transaction to the acquirer, which routes it to the issuer through the network for an authorization decision.

initiate the authorization at the point of sale, the e-commerce checkout, or the recurring-billing schedule
route the authorization request through the acquirer to the network to the issuer
approve the authorization against the cardholder's available credit or available balance
decline the authorization on insufficient funds, suspected fraud, expired card, or velocity-limit breach
hold the authorization on the cardholder's account against the authorization expiration window
release the authorization when the merchant cancels the transaction before capture
capture the funds within the network-mandated capture window (typically seven days for card-present, thirty days for card-not-present)
re-authorize the transaction when the capture window expires before fulfillment
split-authorize the transaction across multiple capture events for backorder or partial-shipment scenarios

Adjacent vocabulary: stand-in authorization (when the issuer is offline, the network approves up to a floor limit on the issuer's behalf), decline code (05 do-not-honor, 14 invalid card, 51 insufficient funds, 54 expired card, 61 exceeds withdrawal limit, 91 issuer unavailable), AVS check (address verification service), CVV2 check (card verification value), 3-D Secure authentication (3DS2 risk-based authentication or step-up challenge), tokenization (network token replacing the PAN throughout the lifecycle), MID (merchant identification number), TID (terminal identification number).

Stage 2 — clearing and settlement (≈24 words)

The captured transaction enters the clearing-and-settlement flow. The acquirer batches the captures and submits them to the network, which routes them to the issuers and orchestrates the inter-bank settlement.

batch the transactions for end-of-day submission
submit the batch to the acquirer for clearing
clear the batch through the network's clearing system on the same business day or the next business day
settle the batch between the acquirer's settlement bank and the issuer's settlement bank
post the settlement to the acquirer's settlement account on the network's settlement cycle
reconcile the settlement against the merchant's submitted batch
flag the settlement variance for investigation when the cleared amount differs from the submitted amount
carry forward the unsettled balance to the next settlement day

Adjacent vocabulary: T+1 settlement (standard for card-present), T+2 settlement (common for card-not-present), settlement holiday (network-defined non-settling days), settlement currency, settlement-currency conversion, DCC (dynamic currency conversion at the point of sale), MCC (merchant category code, used for interchange-tier assignment and reward-program qualification), net settlement, gross settlement, multilateral net settlement.

Stage 3 — funding and merchant pay-out (≈20 words)

The settled funds flow from the acquirer to the merchant's nominated bank account.

fund the merchant account on a same-day, next-day, or two-day funding cycle
hold the funds in a reserve account against rolling-reserve, tiered-reserve, or transactional-reserve policy
release the held funds on the reserve-release schedule
withhold the funds on the merchant's risk profile, the chargeback exposure, or the network-mandated holdback
net the fees from the gross transaction amount on a daily or monthly basis
gross-bill the merchant for the fees on a monthly invoice (alternative to daily netting)
deduct the interchange fee, the assessment fee, and the acquirer markup from the merchant settlement

Adjacent vocabulary: funding day, funding cut-off, funding-cycle latency, rolling reserve (typically 5-10 percent for 90-180 days), tiered reserve (reserve scales with chargeback ratio), transactional reserve (per-transaction holdback), merchant statement, residual report, ISO residual (independent sales organization), ISV revenue share (independent software vendor partner economics).

Stage 4 — fees and economics (≈22 words)

The economics of the transaction are a stacked fee schedule — interchange, assessments, acquirer markup, and gateway fees — that gets tested as a unit on Part 6.

assess the interchange fee on the issuer's interchange schedule (network-set, paid by the acquirer to the issuer)
assess the network fee (assessments, network access fee, acquirer brand fee)
assess the acquirer markup on an interchange-plus, blended-rate, or tiered-pricing model
assess the gateway fee on a per-transaction or monthly basis
qualify the transaction for a lower-interchange tier (card-present with chip read versus card-not-present)
downgrade the transaction to a higher-interchange tier on missing data, late authorization, or non-qualifying merchant data
surcharge the cardholder where surcharging is permitted (US, Canada with restrictions; prohibited in many jurisdictions)
cash-discount the transaction when offering a cash-payment discount in lieu of a surcharge

Adjacent vocabulary: interchange-plus pricing (interchange + assessments + acquirer markup, transparently disclosed), blended pricing (a single all-in rate), tiered pricing (qualified, mid-qualified, non-qualified buckets), flat-rate pricing (Stripe and Square-style 2.9% + 30 cents), effective rate, take rate, attach rate, value-added service fee, Level 2 data (commercial card with tax amount and merchant reference), Level 3 data (commercial card with line-item detail and ship-to-zip), large-ticket interchange, corporate-card interchange.

Stage 5 — chargebacks and dispute resolution (≈26 words)

A cardholder disputes a transaction. The chargeback cycle is the densest sub-cluster in the lifecycle and the one that ETS tests most aggressively because it generates the highest volume of merchant-acquirer email traffic.

initiate the chargeback on the cardholder's dispute claim
assign the reason code (4837 no cardholder authorization, 4853 cardholder dispute, 4855 goods or services not received, 4863 fraud-card-absent environment, 4870 chip-card counterfeit transaction)
route the chargeback from the issuer to the network to the acquirer to the merchant
debit the merchant account for the chargeback amount plus the chargeback fee
representent the chargeback with compelling evidence within the representment window (typically 45-60 days)
accept the chargeback when representment is not commercially worthwhile
win the representment when the issuer accepts the compelling evidence
lose the representment when the issuer re-presents the chargeback
escalate to pre-arbitration when the second chargeback is contested
escalate to arbitration at the network when pre-arbitration fails
accept the arbitration ruling as final and binding

Adjacent vocabulary: compelling evidence (delivery confirmation, AVS match, CVV match, IP-address-to-billing-address match, prior transaction history, signed receipt), chargeback ratio (chargebacks divided by transactions, network-monitored thresholds), excessive-chargeback program (Visa Dispute Monitoring Program, Mastercard Excessive Chargeback Merchant program), early-warning program, fraud-monitoring program (Visa Fraud Monitoring Program, Mastercard ATH program), retrieval request (issuer's pre-chargeback evidence request), first chargeback, second chargeback, pre-arbitration, arbitration, good-faith collection.

Stage 6 — compliance and risk (≈18 words)

The transaction lifecycle is governed by network rules, PCI standards, and regulatory requirements.

maintain PCI DSS compliance on a quarterly self-assessment-questionnaire or annual report-on-compliance basis
undergo the ASV scan (approved scanning vendor) on a quarterly cadence
segment the cardholder-data environment to reduce PCI scope
tokenize the PAN to remove cardholder data from the merchant environment
comply with the network rules on a per-network basis (Visa, Mastercard, Amex, Discover, JCB, UnionPay)
file the PCI Forensic Investigator report in the event of a suspected breach
notify the affected cardholders within the regulatory notification window
report the suspected money laundering via the SAR (suspicious activity report) where applicable

Adjacent vocabulary: PCI DSS 4.0 (current standard as of 2025), SAQ-A, SAQ-A-EP, SAQ-D, ROC (report on compliance), QSA (qualified security assessor), P2PE (point-to-point encryption), DCC compliance, PSD2 SCA requirement (strong customer authentication in Europe), TPP authorization (third-party provider authorization for open banking), MLR compliance (money-laundering regulations), OFAC screening (Office of Foreign Assets Control sanctions screening), AML KYC (anti-money-laundering know-your-customer).

Three drills that move the cluster from passive recognition to productive command

Recognizing the words on the page is not the same as producing them under timed conditions. Three drills move the cluster across that gap.

Drill 1 — the chargeback representment dictation. Take a 220-word representment cover letter from a merchant operations analyst to an acquirer chargeback team (reason code 4853 surfaced, compelling evidence enumerated, AVS match documented, delivery confirmation attached, representment window deadline flagged). Read it aloud once at native pace. Then reconstruct it from memory in writing within seven minutes, populating the cluster vocabulary into the correct lifecycle-stage slots.

Drill 2 — the funding-delay rewrite. Take a generic funding-delay notification email and rewrite it as a payments-funding-delay notice, substituting at least twelve cluster collocations across the settlement, funding, and reconciliation stages. Verify the substituted text against the cluster list above.

Drill 3 — the interchange-downgrade dictation. Take a 160-word email from an acquirer relationship manager to a merchant CFO that explains a recurring interchange downgrade. Reconstruct the email from memory in five minutes, ensuring the qualifying-tier, downgrade-reason, Level-2-data, Level-3-data, and effective-rate-impact collocations are all deployed in the correct positions.

The eight collocations ETS recycles every test cycle

Across the past twenty-four months of TOEIC Link administrations, eight payments-and-card-networks collocations have recurred in Part 6 with disproportionate frequency. Burn these eight into productive memory before test day:

route the authorization request through the acquirer to the network to the issuer
capture the funds within the network-mandated capture window
settle the batch on the T+1 settlement cycle
fund the merchant account on the next-day funding cycle
assess the interchange fee on the issuer's interchange schedule
representent the chargeback with compelling evidence within the representment window
maintain PCI DSS compliance on the quarterly self-assessment cadence
tokenize the PAN to remove cardholder data from the merchant environment

These eight collocations are the spine of the cluster. Every other word in the 160-word inventory clips into one of these eight collocation patterns.

Where this cluster fits in the broader cluster-building program

The payments-and-card-networks cluster is one of the financial-infrastructure verticals in our cluster-building track. It pairs naturally with the banking-and-investment cluster (shared interbank-settlement and treasury vocabulary), the retail-and-ecommerce cluster (shared checkout, fraud-screening, and refund vocabulary), and the cybersecurity-and-information-security cluster (shared PCI, tokenization, and breach-response vocabulary).

Treat this cluster as a single 160-word unit. Drill it as a unit. The Part 6 items that test it will not isolate words from across the lifecycle — they will write passages that move through the lifecycle from authorization through clearing through settlement through funding through reconciliation through chargeback, and the only way to track that arc on a timed test is to have the entire cluster ready as a network of pre-committed collocations rather than as a set of independent lexical items.