What Is an Acquirer BIN? The Bank a Processor Answers To
A Visa card payment carries a six-digit code for the acquiring bank. Scheme rules make that bank liable for the store, so its risk rules reach the checkout.
Ask what is an acquirer BIN and a processor usually points to a field in its API. Card scheme rules point to a bank. Visa's rulebook now calls the number an Acquiring Identifier and defines it as “A 6-digit identifier licensed by Visa to an Acquirer and that is used to identify an Acquirer.”
That short code tells a store more about its payments than most processor dashboards ever do.
It points to the bank that signed the store, the country its licence covers and the party Visa holds liable when a merchant breaks the rules.
Visa is also tightening disclosure around these numbers this month. From 24 October 2026, Visa members in the US and Canada must disclose to Visa the Acquiring Identifiers, BINs and other numeric IDs used by each of their third party agents.
We read the April 2026 Visa Core Rules, the June 2026 Mastercard Rules, Visa's monitoring fact sheet and the published pages of several processors. The processor runs the software for the store. The bank behind it sets the risk rules.
Do not stop at the processor's name when reading a merchant contract or a statement.
What is an acquirer BIN in the card scheme rules?
An acquirer BIN is the six-digit number a card scheme licenses to the bank that signs merchants. The scheme uses it to identify that bank.
Visa's current glossary keeps the word BIN for card issuers, with six digits for numbers licensed before 22 April 2022 and eight digits in the newer form, and it gives acquiring banks a separate term.
Processor documentation still uses the older name for acquirers. A Cybersource field reference calls the value acquirerBin. The mReports merchant reporting manual labels it Acquirer BIN.
Mastercard files the idea under a wider label. Its rulebook treats an ICA, a BIN or an Acquirer Reference ID as a Corporation Asset. Rule 3.2 says the customer holding one “is responsible to the Corporation and to all other Customers for Transactions arising from the use of such Corporation Asset”.
Each number has exactly one owner in Visa's system. The licensing rule states that “A BIN or an Acquiring Identifier may have only one BIN Licensee or Acquiring Identifier Licensee.”
That owner is not always the bank a store deals with in its contract or on its statement.
Visa lets an Associate-Type Member either license its own number or use one licensed to its sponsoring Principal-Type Member, and a Participant-Type Member has no right to license one at all. It uses the number its sponsor designates. In those cases the licensee behind the code is the sponsor bank, not the member using it.
Ownership cannot be traded away under Visa's rules either. A licensee may not sell, rent or exchange the number. When a portfolio is sold or two members merge, the licensee has to report it to Visa.
Unused numbers do not stay with a bank for long, because Visa recovers an identifier that stays uninstalled in its systems for twelve months after assignment.
The code on a transaction works like a licence plate with one registered keeper.
That keeper is a scheme member with an acquiring licence, whatever brand sits on the checkout page.
Acquirer vs processor: which one holds the licence?
The acquirer holds the scheme licence, and the processor runs the technology on the acquirer's behalf. Visa's glossary draws the line in one entry. It describes an Acquirer Processor as “A non-Member agent or processor that a Member has engaged to support its Visa acquiring business.”
Visa defines the acquirer itself as a Member that signs a Merchant or Payment Facilitator and directly or indirectly enters a Transaction into Interchange.
Liability follows the licence rather than the software. Under Visa's rule 1.1.8.22 a Member is responsible for any and all losses caused by its VisaNet Processor, and every Member using that processor shares responsibility for its proper performance under the Visa Rules.
Registration works the same way, bank by bank. Each acquirer must register separately any third party agent that uses its Acquiring Identifier or serves its merchants.
Stripe's explainer on acquirer vs processor, published in its resources library, splits the work in a similar place. It gives processors the technical side and acquirers the financial piece. The page adds that “The acquirer is responsible for underwriting the merchant account and assuming some level of risk in case of disputes or chargebacks.”
The same page presents Stripe as both processor and acquirer, so its customers need no separate merchant account.
Stripe's legal acquirer disclosure gives the detail country by country. For the European Economic Area it names Stripe Technology Europe as the acquirer for Visa and Mastercard transactions. For the United States it lists Stripe, LLC as a payment facilitator of several banks, with Cross River Bank among them.
One brand can stand in two different places in the chain, depending on the country of the account. A marketing page answers the question in general terms. A legal page answers it for one country.
Where does a store find its acquirer BIN?
A store can meet the number in dispute and refund references, in 3-D Secure settings and in its processor's reporting portal, and each of them presents it in a different form.
Dispute and refund references carry it inside a longer number. Stripe's guide describes the ARN as a 23-digit reference attached by the acquiring bank.
For a typical Visa ARN it lists “A six-digit segment that identifies which acquiring bank processed the transaction”.
Visa and Mastercard lay those digits out differently, the guide warns, so the same string carries different information on each network. Refunds also get their own ARN.
Authentication settings carry the same number in plain sight. Cybersource's field for 3-D Secure asks for an “Acquirer bank ID number that corresponds to a certificate that Cybersource already has.” Visa values start with 4 and Mastercard values with 5.
Reporting portals are the third place a finance team can look for the bank's number. The mReports manual defines its field plainly: “The acquirer BIN identifies the member bank that signed the merchant using the POS application.”
Not every six-digit BIN on a report belongs to Visa, though.
Another manual on the same mReports portal uses BIN for a number that TSYS Acquiring Solutions assigns to a client bank, and that number sits at the top of the processor's own routing hierarchy.
The contract remains the cleanest source of all. Visa's rules for US merchant agreements require them to clearly and obviously specify the Acquirer's name and location. Visa's UK guidance for merchants puts the same advice in one line: “Make sure the contract has the name of the acquirer clearly identified.”
UK law adds a statement duty for every card payment. Article 12 of the interchange fee regulation, in the version on legislation.gov.uk, makes the payee's provider supply “the reference enabling the payee to identify the card-based payment transaction”.
Article 12 also requires the amount, in the currency in which the payee's payment account is credited. Charges must show the merchant service charge and the interchange fee separately.
That page also carries a note that a 2023 Act revokes the regulation, a change not yet applied to the text.
Why does the bank behind the processor set the rules?
The bank sets the rules because Visa and Mastercard bill it, fine it and hold it liable for everything done under its number. Visa's rule 2.2.1.1 makes a principal member “liable for all activities associated with any BIN or Acquiring Identifier that it licenses”.
The cost of a bad merchant lands on the bank first, under a rule written for acquirers. Visa's rule 1.9.1.5 says “An Acquirer is responsible for all costs incurred by Visa due to the Acquirer’s failure to terminate a Merchant”. Those costs include attorney's fees and the cost of Visa's legal action.
The rule also covers a failure to cut off payment facilitators, marketplaces and sponsored merchants, so a bank facing such a bill has every reason to write termination rights into its contracts and to use them early.
Fines travel along the same route to the merchant. Under Visa's rule 1.11.2.5 the member pays every non-compliance assessment itself, whether it absorbs the charge, passes it on or increases it when billing its customer.
That rule also bars a member from telling its customer that Visa imposes the assessment on the customer, so in our view a statement line blaming a Visa fine on the store deserves a direct question.
The scheme pushes its rules into the merchant contract itself. Rule 1.5.2.1 requires every merchant agreement to oblige the merchant to follow the Visa Rules on acceptance, risk management and transaction processing.
Even a retry after a declined payment sits under the bank's licence and the scheme's data rules. Visa's rule 1.7.2.1 bars an acquirer, merchant, payment facilitator or processor from intentionally manipulating data from the original request when it retries after a decline, and the Acquiring Identifier is first on the list, ahead of merchant country and MCC.
A processor's terms carry the bank's duties forward. The bank's duties come from the scheme. A store reading only the processor's terms sees the last link of that chain and none of the others.
How does one bank's portfolio change the rules for a store?
Visa measures fraud and disputes across each acquirer's whole book as well as for single merchants. Its 2025 fact sheet on the Visa Acquirer Monitoring Program says that each month Visa checks fraud, dispute and enumeration levels and identifies the acquirers or merchants above its thresholds.
The core measure is a simple ratio of counts. Visa adds reported fraud and disputes on card-not-present transactions. It then divides the total by the count of settled transactions.
An acquirer's portfolio is labelled Above Standard at fifty basis points and Excessive at seventy, and the separate merchant thresholds apply only when the acquirer sits in neither group.
Those merchant lines sit well above the acquirer ones.
What follows a flag is spelled out in a single sentence: “Entities identified as exceeding program thresholds are required to implement risk mitigation control measures.”
Our reading is that a store's own numbers are judged inside its bank's numbers, so when a bank's portfolio crosses the line, its required controls can reach stores that did not cross any line themselves. That is our inference, not Visa's wording.
The program also requires acquirers to take proactive steps against merchants exceeding enumeration limits. Those limits count approved and declined authorisation attempts.
The duty for enumeration sits with the bank. The checks it picks to meet that duty land on the merchants in its book.
Does the country behind an acquirer BIN matter for cross-border sales?
It does, because both schemes tie the number to a country where the bank holds a licence. Visa's rule 1.2.1.1 says “A BIN or an Acquiring Identifier is licensed for use in a single country”, with exceptions for named programs and for EU passporting in the Europe Region.
Mastercard says the same thing in its own words. Its licence rule requires the ICA number and BIN used for acquiring to reflect a country in the customer's Area of Use where the merchants are located.
For online sales, Visa fixes that location by rule. The acquirer must assign the country of the merchant's principal place of business as the merchant outlet location for card-absent transactions.
Travel, lodging and vehicle rental merchants get extra options. Other merchants can add a location only where they pass a set of tests, such as a permanent site with staff and sales tax charged there.
Under that rule a store in the UK that sells online to buyers in France still has its card-absent sales located in the UK.
The merchant outlet country also has to stay the same for the whole life of a transaction. Authorization, clearing, disputes and refunds all carry it.
Read together, the two rulebooks expect the acquirer BIN on those sales to be licensed for use in the UK, and a gap between the store's country and the licence country is worth raising with the processor before renewal.
What do the rules and processor pages leave out?
The documents explain who is liable, but they give a merchant no simple way to check the number itself. Visa's rules have members file contact data for each identifier in a Client Directory on Visa Access, and we found no public lookup for merchants in the documents we read.
Processor pages stop short in a similar way. Stripe's US disclosure names several banks without saying which one serves a given account.
The monitoring data also stays out of public view. Visa's fact sheet gives the thresholds but no count of flagged acquirers or merchants, and neither figure is published elsewhere in the material we read.
Names differ between the schemes and the portals as well. Visa says Acquiring Identifier, Mastercard groups ICA, BIN and ARID together, and some portals use BIN for their own routing numbers. The documents give different answers to a plain naming question.
Even the word BIN changes meaning from page to page.
A payments lawyer can read a merchant agreement against these rules, an accountant can trace the fee lines, and the acquiring bank itself can confirm which identifier carries a store's transactions.
Where do we expect acquirer disclosure to go next?
So what is an acquirer BIN to a store? Our view is that it is the most honest line in the payment chain. A scheme licence sits behind it. One bank holds it, and that bank answers to the scheme for every sale made under it.
The next step is already written into Visa's rulebook. From 24 October 2026, US and Canadian members must disclose to Visa the identifiers each third party agent uses, keep that information current and review it every year. That rule takes effect this month.
UK merchants already get more on paper from their regulator. The Payment Systems Regulator directed 14 firms to send summary boxes and trigger messages from July 2023. It said it would monitor their compliance and the impact of the remedies to decide on further action.
We expect more stores to ask one plain question at renewal: which bank holds the number our sales run on, and where is it licensed.
The answer tells a store whose rulebook it is really trading under, and which bank to call.
Sources
- Visa Core Rules and Visa Product and Service Rules, 18 April 2026 usa.visa.com.
- Mastercard Rules, 2 June 2026 mastercard.com.
- Visa Acquirer Monitoring Program Overview (fact sheet, 2025) corporate.visa.com.
- Visa UK: Choosing an Acquirer visa.co.uk.
- Regulation (EU) 2015/751, Article 12 (UK version) legislation.gov.uk.
- Payment Systems Regulator, PS22/2 Card-acquiring market remedies: final decision psr.org.uk.
- Stripe: Acquirer Disclosure and Acquirer Terms stripe.com.
- Stripe: Payment processor vs. merchant acquirer stripe.com.
- Stripe: What is an acquirer reference number (ARN)? stripe.com.
- Cybersource API field reference: acquirerInformation.acquirerBin developer.cybersource.com.
- mReports documentation: Acquirer BIN mreports.com.
- mReports documentation: Quick Search (BIN hierarchy) mreports.com.