Allowed Card Networks {#ctp-cc-allowed-card-networks}
=====================================================

Use the allowedCardNetworks field to define the card types.  
These card networks are available for card entry:

* American Express (supported on `Click to Pay`)
* Cartes Bancaires
* Carnet
* China UnionPay
* Diners Club
* Discover
* EFTPOS
* ELO
* Jaywan
* JCB
* JCrew
* KCP
* mada
* Maestro
* Mastercard (supported on `Click to Pay`)
* Meeza
* PayPak
* UATP
* Visa (supported on `Click to Pay`)
  {#ctp-cc-allowed-card-networks_ul_cz5_tt1_3jc}  
  To support dual-branded or co-badged cards, you must list your supported card type values for the allowedCardNetworks field based on your preference for processing card numbers. For example, if a card is dual-branded as Visa and Cartes Bancaires, and Cartes Bancaires is listed first, the card type is set to Cartes Bancaires after the card number is entered in your `Unified Checkout` card collection form. For information on dual-branded or co-badged cards, see [Dual-Branded Cards](/docs/cybs/en-us/click-to-pay/developer/all/rest/click-to-pay/ctp-tokens-intro/ctp-dual-co-brand-card-support.md "").

> IMPORTANT  
> Some card types, such as KCP and UATP, do not have security codes (CVV or CVN). If you include only card types that do not have security codes in the allowedCardNetworks field, ` Unified Checkout ` does not display the security code field in the UI.  
> If you include card types that do not have security codes and cards types that do have security codes in the allowedCardNetworks field, ` Unified Checkout ` displays the security code field in the UI. The field is disabled in the UI when the cardholder enters a card number for a card type with no security code

Domestic Scheme Rules {#ctp-cc-allowed-card-networks_section_jf1_syt_dkc}
-------------------------------------------------------------------------

For markets where domestic routing, network preference, or co-badging regulations apply, you are responsible for ensuring that domestic payment schemes are prioritized appropriately within the allowedCardNetworks configuration.  
In these scenarios, domestic schemes must be listed ahead of international networks such as Visa or Mastercard where required by local regulations or scheme rules.  
If network preference varies by transaction, the order of networks should be dynamically configured when you create the capture context request using the Sessions API.  
You are responsible for reviewing and complying with all applicable local regulatory, scheme, and acquirer requirements relating to domestic routing and network selection.