Skip to content

Sec. 235.7 - Limitation on payment card restrictions. *


This section is amended, effective July 1, 2023. The amendments are shown below in THIS COLOR TEXT.

[Notice: Applicable sections of Appendix A – Official Board Commentary – are included below this section of the regulation.]

 

(a) Prohibition on network exclusivity. (1) In general. An issuer or payment card network shall not directly or through any agent, processor, or licensed member of a payment card network, by contract, requirement, condition, penalty, or otherwise, restrict the number of payment card networks on which an electronic debit transaction may be processed to less than two unaffiliated networks.

(2) Permitted arrangements. An issuer satisfies the requirements of paragraph (a)(1) of this section only if the issuer allows an electronic debit transaction to be processed on at least two unaffiliated payment card networks, each of which does not, by rule or policy, restrict the operation of the network to a limited geographic area, specific merchant, or particular type of merchant or transaction, and each of which has taken steps reasonably designed to enable the network to process the electronic debit transactions that the network would reasonably expect will be routed to it, based on expected transaction volume.

Editor's Note: Effective July 1, 2023, section 235.7(a)(2) is revised to read:

(2) Permitted arrangements. An issuer satisfies the requirements of paragraph (a)(1) of this section only if the issuer enables at least two unaffiliated payment card networks to process an electronic debit transaction —

(i) Where such networks in combination do not, by their respective rules or policies or by contract with or other restriction imposed by the issuer, result in the operation of only one network or only multiple affiliated networks for a geographic area, specific merchant, particular type of merchant, or particular type of transaction, and

(ii) Where each of these networks has taken steps reasonably designed to be able to process the electronic debit transactions that it would reasonably expect will be routed to it, based on expected transaction volume.

(3) Prohibited exclusivity arrangements by networks. For purposes of paragraph (a)(1) of this section, a payment card network may not restrict or otherwise limit an issuer’s ability to contract with any other payment card network that may process an electronic debit transaction involving the issuer’s debit cards.

(4) Subsequent affiliation. If unaffiliated payment card networks become affiliated as a result of a merger or acquisition such that an issuer is no longer in compliance with paragraph (a) of this section, the issuer must add an unaffiliated payment card network through which electronic debit transactions on the relevant debit card may be processed no later than six months after the date on which the previously unaffiliated payment card networks consummate the affiliation.

(b) Prohibition on routing restrictions. An issuer or payment card network shall not, directly or through any agent, processor, or licensed member of the network, by contract, requirement, condition, penalty, or otherwise, inhibit the ability of any person that accepts or honors debit cards for payments to direct the routing of electronic debit transactions for processing over any payment card network that may process such transactions.

(c) Effective dates. (1) General. Except as otherwise provided in paragraphs (c)(2), (c)(3), and (c)(4) of this section, paragraph (a) of this section becomes effective on April 1, 2012. Paragraph (b) of this section becomes effective on October 1, 2011.

(2) Restrictions by payment card networks. Paragraphs (a)(1) and (a)(3) of this section become effective for payment card networks on October 1, 2011.

(3) Debit cards that use transaction qualification or substantiation systems. Issuers shall comply with the requirements of paragraph (a) of this section by April 1, 2013, for electronic debit transactions using debit cards that use point-of-sale transaction qualification or substantiation systems for verifying the eligibility of purchased goods or services.

(4) General-use prepaid cards. Issuers shall comply with the requirements of paragraph (a) of this section with respect to general-use prepaid cards as set out below.

(i) With respect to non-reloadable general-use prepaid cards, the effective date is April 1, 2013. Non-reloadable general-use prepaid cards sold prior to April 1, 2013 are not subject to paragraph (a) of this section.

(ii) With respect to reloadable general-use prepaid cards, the effective date is April 1, 2013. Reloadable general-use prepaid cards sold prior to April 1, 2013 are not subject to paragraph (a) of this section unless and until they are reloaded, in which case the following effective dates apply:

(A) With respect to reloadable general-use prepaid cards sold and reloaded prior to April 1, 2013, the effective date is May 1, 2013.

(B) With respect to reloadable general-use prepaid cards sold prior to April 1, 2013, and reloaded on or after April 1, 2013, the effective date is 30 days after the date of reloading.

 

Official Board Commentary

 

1. Application of small issuer, government-administered payment program, and reloadable card exemptions to payment card network restrictions. The exemptions under § 235.5 for small issuers, cards issued pursuant to government-administered payment programs, and certain reloadable prepaid cards do not apply to the limitations on payment card network restrictions. For example, debit cards for government-administered payment programs, although exempt from the restrictions on interchange transaction fees, are subject to the requirement that electronic debit transactions made using such cards must be capable of being processed on at least two unaffiliated payment card networks and to the prohibition on inhibiting a merchant’s ability to determine the routing for electronic debit transactions.

7(a) Prohibition on network exclusivity

1. Scope of restriction. Section 235.7(a) requires a debit card subject to the regulation to be enabled on at least two unaffiliated payment card networks. This paragraph does not, however, require an issuer to have two or more unaffiliated networks available for each method of cardholder authentication. For example, it is sufficient for an issuer to issue a debit card that operates on one signature-based card network and on one PIN-based card network, as long as the two card networks are not affiliated. Alternatively, an issuer may issue a debit card that is accepted on two unaffiliated signature-based card networks or on two unaffiliated PIN-based card networks. See also comment 7(a)-7.

2. Permitted networks. i. A smaller payment card network could be used to help satisfy the requirement that an issuer enable two unaffiliated networks if the network was willing to expand its coverage in response to increased merchant demand for access to its network and it meets the other requirements for a permitted arrangement, including taking steps reasonably designed to enable it to process the electronic debit transactions that it would reasonably expect to be routed to it. If, however, the network’s policy or practice is to limit such expansion, it would not qualify as one of the two unaffiliated networks.

ii. A payment card network that is accepted only at a limited category of merchants (such as a particular grocery store chain, merchants located in a particular shopping mall, or a single class of merchants, such as grocery stores or gas stations) would not satisfy the rule.

iii. One of the steps a network can take to form a reasonable expectation of transaction volume is to consider factors such as the number of cards expected to be issued that are enabled on the network and expected card usage patterns.

3. Examples of prohibited network restrictions on an issuer’s ability to contract. The following are examples of prohibited network restrictions on an issuer’s ability to contract with other payment card networks:

i. Network rules or contract provisions limiting or otherwise restricting the other payment card networks that may be enabled on a particular debit card, or network rules or contract provisions that specify the other networks that may be enabled on a particular debit card.

ii. Network rules or guidelines that allow only that network’s (or its affiliated network’s) brand, mark, or logo to be displayed on a particular debit card, or that otherwise limit the ability of brands, marks, or logos of other payment card networks to appear on the debit card.

4. Network logos or symbols on card not required. Section 235.7(a) does not require that a debit card display the brand, mark, or logo of each payment card network over which an electronic debit transaction may be processed. For example, this rule does not require a debit card that is enabled for two or more unaffiliated payment card networks to bear the brand, mark, or logo for each card network.

5. Voluntary exclusivity arrangements prohibited. Section 235.7(a) requires the issuance of debit cards that are enabled on at least two unaffiliated payment card networks, even if the issuer is not subject to any rule of, or contract or other agreement with, a payment card network requiring that all or a specified minimum percentage of electronic debit transactions be processed on the network or its affiliated networks.

6. Affiliated payment card networks. Section 235.7(a) does not prohibit an issuer from including an affiliated payment card network among the networks that may process an electronic debit transaction with respect to a particular debit card, as long as at least two of the networks that are enabled on the card are unaffiliated. For example, an issuer may offer debit cards that are accepted on a payment card network for signature debit transactions and on an affiliated payment card network for PIN debit transactions as long as those debit cards may also be accepted on another unaffiliated payment card network.

7. Application of rule regardless of form factor. The network exclusivity provisions in § 235.7(a) require that all debit cards be enabled on at least two unaffiliated payment card networks for electronic debit transactions, regardless of whether the debit card is issued in card form. This applies to any supplemental device, such as a fob or token, or chip or application in a mobile phone, that is issued in connection with a plastic card, even if that plastic card fully complies with the rule.

Editor's Note: Effective July 1, 2023, paragraph 7(a) is revised to read:

1. Scope of restriction. Section 235.7(a) requires an issuer to configure each of its debit cards so that each electronic debit transaction performed with such card can be processed on at least two unaffiliated payment card networks. In particular, § 235.7(a) requires this condition to be satisfied for each geographic area, specific merchant, particular type of merchant, and particular type of transaction for which the issuer's debit card can be used to perform an electronic debit transaction. As long as the condition is satisfied for each such case, § 235.7(a) does not require the condition to be satisfied for each method of cardholder authentication (e.g., signature, PIN, biometrics, any other method of cardholder authentication that may be developed in the future, or the lack of a method of cardholder authentication). For example, it is sufficient for an issuer to issue a debit card that can perform signature-authenticated transactions only over one payment card network and PIN-authenticated transactions only over another payment card network, as long as the two payment card networks are not affiliated and each network can be used to process electronic debit transactions for every geographic area, specific merchant, particular type of merchant, and particular type of transaction for which the issuer's debit card can be used to perform an electronic debit transaction.

2. Issuer’s role. Section 235.7(a) does not require an issuer to ensure that two or more unaffiliated payment card networks will actually be available to the merchant to process every electronic debit transaction. To comply with the requirement in § 235.7(a), it is sufficient for an issuer to configure each of its debit cards so that each electronic debit transaction performed with such card can be processed on at least two unaffiliated payment card networks, even if the networks that are actually available to the merchant for a particular transaction are limited by, for example, the card acceptance technologies that a merchant adopts, or the networks that the merchant accepts.

3. Permitted networks

i. Network volume capabilities. A payment card network could be used to satisfy the requirement that an issuer enable two unaffiliated payment card networks for each electronic debit transaction if the network was either (a) capable of processing the volume of electronic debit transactions that it would reasonably expect to be routed to it or (b) willing to expand its capabilities to meet such expected transaction volume. If, however, the network’s policy or practice is to limit such expansion, it would not qualify as one of the two unaffiliated payment card networks.

ii. Reasonable volume expectations. One of the steps a payment card network can take to form a reasonable expectation of its transaction volume is to consider factors such as the number of cards expected to be issued that are enabled by an issuer on the network and expected card usage patterns.

iii. Examples of permitted arrangements. For each geographic area (e.g., New York State), specific merchant (e.g., a specific fast food restaurant chain), particular type of merchant (e.g., fast food restaurants), and particular type of transaction (e.g., card-not-present transaction) for which the issuer's debit card can be used to perform an electronic debit transaction, an issuer must enable at least two unaffiliated payment card networks, but those payment card networks do not necessarily have to be the same two payment card networks for every transaction.

A. Geographic area: An issuer complies with the rule only if, for each geographic area in which the issuer's debit card can be used to perform an electronic debit transaction, the issuer enables at least two unaffiliated payment card networks. For example, an issuer could comply with the rule by enabling two unaffiliated payment card networks that can each process transactions in all 50 U.S. states. Alternatively, the issuer could comply with the rule by enabling three unaffiliated payment card networks, A, B, and C, where network A can process transactions in all 50 U.S. states, network B can process transactions in the 48 contiguous United States, and network C can process transactions in Alaska and Hawaii.

B. Particular type of transaction: An issuer complies with the rule only if, for each particular type of transaction for which the issuer's debit card can be used to perform an electronic debit transaction, the issuer enables at least two unaffiliated payment card networks. For example, an issuer could comply with the rule by enabling two unaffiliated payment card networks that can each process both card-present and card-not-present transactions. Alternatively, the issuer could comply with the rule by enabling three unaffiliated payment card networks, A, B, and C, where network A can process both card-present and card-not-present transactions, network B can process card-present transactions, and network C can process card-not-present transactions.

4. Examples of prohibited network restrictions on an issuer's ability to contract with other payment card networks. The following are examples of prohibited network restrictions on an issuer's ability to contract with other payment card networks:

i. Network rules or contract provisions limiting or otherwise restricting the other payment card networks that an issuer may enable on a particular debit card, or network rules or contract provisions that specify the other networks that an issuer may enable on a particular debit card.

ii. Network rules or guidelines that allow only that payment card network's (or its affiliated networks') brand, mark, or logo to be displayed on a particular debit card, or that otherwise limit the ability of brands, marks, or logos of other payment card networks to appear on the debit card.

5. Network logos or symbols on card not required. Section 235.7(a) does not require that a debit card display the brand, mark, or logo of each payment card network over which an electronic debit transaction may be processed. For example, the rule does not require a debit card that an issuer enables on two or more unaffiliated payment card networks to bear the brand, mark, or logo of each such payment card network.

6. Voluntary exclusivity arrangements prohibited. Section 235.7(a) requires that an issuer enable at least two unaffiliated payment card networks to process an electronic debit transaction, even if the issuer is not subject to any rule of, or contract or other agreement with, a payment card network requiring that all or a specified minimum percentage of electronic debit transactions be processed on the network or its affiliated networks.

7. Affiliated payment card networks. Section 235.7(a) does not prohibit an issuer from enabling two affiliated payment card networks among the networks on a particular debit card, as long as at least two of the networks that can be used to process each electronic debit transaction are unaffiliated.

8. Application of rule regardless of form. The network exclusivity provisions in § 235.7(a) apply to electronic debit transactions performed with any debit card as defined in § 235.2, regardless of the form of such debit card. For example, the requirement applies to electronic debit transactions performed using a plastic card, a supplemental device such as a fob, information stored inside an ewallet on a mobile phone or other device, or any other form of debit card, as defined in § 235.2, that may be developed in the future.

7(b) Prohibition on routing restrictions

1. Relationship to the network exclusivity restrictions. An issuer or payment card network is prohibited from inhibiting a merchant’s ability to route or direct an electronic debit transaction over any of the payment card networks that the issuer has enabled to process an electronic debit transaction for that particular debit card. This rule does not permit a merchant to route the transaction over a network that the issuer did not enable to process transactions using that debit card.

2. Examples of prohibited merchant restrictions. The following are examples of issuer or network practices that would inhibit a merchant’s ability to direct the routing of an electronic debit transaction that are prohibited under § 235.7(b):

i. Prohibiting a merchant from encouraging or discouraging a cardholder’s use of a particular method of debit card authorization, such as rules prohibiting merchants from favoring a cardholder’s use of PIN debit over signature debit, or from discouraging the cardholder’s use of signature debit.

ii. Establishing network rules or designating issuer priorities directing the processing of an electronic debit transaction on a specified payment card network or its affiliated networks, or directing the processing of the transaction away from a specified network or its affiliates, except as a default rule in the event the merchant, or its acquirer or processor, does not designate a routing preference, or if required by state law.

iii. Requiring a specific payment card network based on the type of access device provided to the cardholder by the issuer.

Editor's Note: Effective July 1, 2023, paragraphs 7(b)(1) and (b)(2) are revised to read:

7(b) Prohibition on Routing Restrictions

1. Relationship to the network exclusivity restrictions. An issuer or payment card network is prohibited from inhibiting a merchant's ability to direct the routing of an electronic debit transaction over any of the payment card networks that the issuer has enabled to process electronic debit transactions performed with a particular debit card. The rule does not require that an issuer allow a merchant to route a transaction over a payment card network that the issuer did not enable to process transactions performed with that debit card.

2. Examples of prohibited merchant restrictions. The following are examples of issuer or network practices that would inhibit a merchant's ability to direct the routing of an electronic debit transaction and that are therefore prohibited under § 235.7(b):

i. Prohibiting a merchant from encouraging or discouraging a cardholder's use of a particular method of cardholder authentication, for example prohibiting merchants from favoring a cardholder's use of one cardholder authentication method over another, or from discouraging the cardholder's use of any given cardholder authentication method, as further described in comment 7(a)-1.

ii. Establishing network rules or designating issuer priorities directing the processing of an electronic debit transaction on a specified payment card network or its affiliated networks, or directing the processing of the transaction away from a specified payment card network or its affiliates, except as (A) a default rule in the event the merchant, or its acquirer or processor, does not designate a routing preference, or (B) if required by state law.

iii. Requiring a specific payment card network to be used based on the form of debit card presented by the cardholder to the merchant (e.g., plastic card, payment code, or any other form of debit card as defined in § 235.2).

3. Merchant payments not prohibited. A payment card network does not restrict a merchant’s ability to route transactions over available payment card networks in violation of § 235.7(b) by offering payments or other incentives to encourage the merchant to route electronic debit card transactions to the network for processing.

4. Real-time routing decision not required. A merchant need not make network routing decisions on a transaction-by-transaction basis. A merchant and its acquirer or processor may agree to a pre-determined set of routing choices that apply to all electronic debit transactions that are processed by the acquirer or processor on behalf of the merchant.

5. No effect on network rules governing the routing of subsequent transactions. Section 235.7 does not supersede a network rule that requires a chargeback or return of an electronic debit transaction to be processed on the same network that processed the original transaction.

Editor's Note: Effective July 1, 2023, paragraph 7(b)5 is revised to read:

5. No effect on network rules governing the routing of subsequent transactions. Section 235.7 does not supersede a payment card network rule that requires a chargeback or return of an electronic debit transaction to be processed on the same network that processed the original transaction.

7(c) Effective date

1. Health care and employee benefit cards. Section 235.7(c)(1) delays the effective date of the network exclusivity provisions for certain debit cards issued in connection with a health care or employee benefit account to the extent such cards use (even if not required) transaction substantiation or qualification authorization systems at point of sale to verify that the card is only used for eligible goods and services for purposes of qualifying for favorable tax treatment under Internal Revenue Code requirements. Debit cards that may qualify for the delayed effective date include, but may not be limited to, cards issued in connection with flexible spending accounts established under section 125 of the Internal Revenue Code for health care related expenses and health reimbursement accounts established under section 105 of the Internal Revenue Code.

 

Banker Tools View All

A collection of useful resources for various areas of the bank which have been developed by members of the BankersOnline staff or have been created and contributed by users of the BankersOnline site.

Banker Tools

Penalties View All

Search Regulations

View Regulations

CFPB Letter Classification

FRB Letter Classification