02.02.2013 Views

Maestro Global Rules (PDF) - MasterCard

Maestro Global Rules (PDF) - MasterCard

Maestro Global Rules (PDF) - MasterCard

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Issuing<br />

6.2 Card Standards and Specifications<br />

It is strongly recommended that Issuers encode extended service code values<br />

120 (or 220)—online authorization, PIN required—on Cards for which<br />

<strong>Maestro</strong> is the primary acceptance brand. Note: This does not apply to<br />

<strong>Maestro</strong>-branded <strong>MasterCard</strong> cards, as the primary acceptance brand in this<br />

instance is <strong>MasterCard</strong>.<br />

The only acceptable values for encoding new or re-issued Cards are as follows:<br />

Position Value Description<br />

1 1 Available for International Interchange<br />

2 Available for International Interchange(alternative<br />

technology—Chip Card)<br />

2 0 Normal authorization<br />

2 Positive online authorization required<br />

3 0 PIN required<br />

1 Normal Cardholder verification, no restrictions<br />

6 Prompt for PIN if PIN pad present<br />

Issuers that encode value “0” (normal authorization) in position 2 of the<br />

extended service code must accept liability for any purchase Transaction<br />

completed at a cardholder-activated terminal (CAT).<br />

Issuers that encode values “1” (normal Cardholder verification, no restrictions)<br />

or “6” (prompt for PIN if PIN entry device present) in position 3 of the extended<br />

service code must not decline Transactions simply because they do not contain<br />

a PIN.<br />

Effective 1 January 2007, all Cards must use the values contained in the chart<br />

above for encoding purposes. No other values will be allowed.<br />

It is recommended that Issuers set authorization parameters that decline any<br />

magnetic stripe Transaction containing the invalid service code value of 000 for<br />

purposes of fraud prevention.<br />

6.2.1.6 Discretionary Data<br />

All other encoded data not listed in Rule 6.2.1.2 is discretionary data, and under<br />

the Issuer’s control.<br />

This data is routed to Issuers for manipulation and verification in messages, as<br />

specified in the applicable technical specifications.<br />

This data must be encoded between the service code and the end sentinel, and<br />

only contain valid characters in accordance with ISO 7813.<br />

It is recommended that the discretionary data field be encoded as specified in<br />

Appendix B, “Technical Specifications.”<br />

©1993–2012 <strong>MasterCard</strong>. Proprietary. All rights reserved.<br />

6-6 9 November 2012 • <strong>Maestro</strong> <strong>Global</strong> <strong>Rules</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!