Card Products in Europe

You receive a BIN from the network, typically 6 or 8 digits in length, and the network provides your splits as part of BIN setup.

Marqeta utilizes a BIN prefix model which allows you to select the first 6 to 10 digits of the primary account number (PAN) specified at the card product level.

It is common for a program to set up multiple card products, usually two per issuing country (one virtual and one physical). This gives you greater control over your cards in certain countries. For example, a BIN prefix of 12345678 issues cards between 1234567800000000 and 1234567899999999.

For any new BIN prefixes that you want to issue against, you should ensure Marqeta is made aware. Marqeta can then enable them within the platform’s router to allow for transactions. Failure to inform Marqeta may result in successful card issuing but failing transactions.

payment_instrument – Determines whether the card is virtual or physical.

card_life_cycle – Determines how your card behaves during its lifetime.

bin_prefix – Determines the prefix of the PAN that is issued. This can be between 6 and 11 digits in length and should be aligned to the network configuration of your BIN. Common setup includes two card products per issuing country (one virtual and one physical).

Marqeta is integrated into several sites with each of the providers, including IDEMIA, NITECREST, and ALLPAY.

Physical cards created on the Marqeta platform are placed into a queue and sent to the card provider once a day. Time changes are based on the chosen provider.

fulfillment_provider – Determines where Marqeta sends the files. Marqeta informs you of the value to set here to ensure proper delivery to your chosen provider’s fulfillment center.

package_id – Determines card design and functionality. This can be used to change card appearance and behavior between card products.

enable_offline_pin – Allows an encrypted PIN to be sent to the card provider for chip personalization. This is required for spending in offline PIN markets, such as the United Kingdom and France, and for use in offline terminals, such as airplanes and toll booths.

service_code – Sets the card type and functionality to determine how the card will function in different terminal scenarios. You and your card provider decide this together during card personalization, and Marqeta should be aware.

programgateway_funding_source – The customer gateway where funding requests are sent. Details of the JIT gateway funding source will define where the requests will be sent. Once a transaction passes Marqeta’s standard checks, approval decisions are delegated to you.

funding_source_token – The designated funding source to use. Funding sources are created through an API. They contain a URL, username, and password for connecting to the customer gateway. For API reference information, see Program Funding Sources.

always_fund – A funding setting for the customer gateway. This setting should always be set to true because it ensures that the full transaction amount is always taken from your program gateway funding source.

poi – Assigns where cards can be used, including:

require_card_not_present_card_security_code – Enforces the presence of the CVV in an authorization request. If the CVV is provided and incorrect, the transaction is declined. Typically recommended to be set to false because, in some instances, merchants send authorization requests without this information. Amazon and Netflix commonly send authorization without this information.

always_require_pin – Blocks any transaction where PIN is not present. Typically not recommended for most customers because it would force PIN and decline e-commerce transactions.

allow_gpa_auth – Allows transactions to be authorized using GPA funds. Must always be true to approve transactions within the card product.

address_verification – Compares the address provided by the merchant to the address on file. If they do not match, you can choose to validate and respond, or decline. Some merchants send reversals if address verification is not performed; some regions mandate this.

accepted_countries_token – Determines the list of countries in which a card can perform transactions. Marqeta must abide by OFAC rules. As such, a default list is put in place. You can request additional countries to be added to the list, if needed.

notification_language – Determines the language for cardholder correspondence. Default language is English.

The individual amount of the contactless transaction does not exceed €50;
AND

The cumulative amount of previous contactless transactions, from the date SCA was last applied, does not exceed €150;
AND

The number of consecutive contactless transactions since SCA was last applied does not exceed five.

Tokenization enablement is a simple configuration that can be enabled at any time on the Marqeta platform. It is contingent upon your tokenization project with the network.

provisioning_controls – A cardholder’s ability to tokenize their physical or virtual card into a mobile wallet. Three types of provisioning which can be independently enabled or disabled: manual, in-app, and card on file. Optionally, you can request step-up verification from Marqeta when there is a mismatch in address verification.

card_art_id – A unique reference to the card art shown with a tokenized card. This value is provided by the network upon uploading image assets and returned by Marqeta during token requests.