Mass Transit Payment Services Using TMS Tokens

You can request these payment services for mass transit using TMS tokens:

Authorization for account verification and debt recovery
Sale for aggregated fares and debt recovery
Stand-alone credit

In the card-present EMV contactless request, include the transient token ID in the

tokenInformation.jti

field in place of track 2 data.

During the tap token creation request, you can include EMV tag-length-value (TLV) tags in the

paymentInformation.fluidData.value

field or as part of the payment transaction request within the

pointOfSaleInformation.emv.tags

field.

If you send EMV tags in the tap token create request, you should not send EMV tags in the payment transaction request.

If EMV TLV tags are present in both the payment transaction and the token vault,

Cybersource

reads the value provided in the payment transaction in preference to the values stored in the vault.

Mastercard EMV transactions include three field values that can be handled automatically:

paymentInformation.card.initiationChannel
pointOfSaleInformation.emv.cardSequenceNumber
pointOfSaleInformation.serviceCode

Your account can be configured to read these values automatically from the EMV TLV tags and track 2 equivalent. When that option is enabled, do not include those three fields in EMV payment requests.

If any of these values are present in both the separate fields and the EMV TLV and track 2 equivalent,

Cybersource

reads the value provided in the separate fields rather than the values present in the EMV TLV and track 2 equivalent.

Merchant initiated card-not-present payment requests use the

paymentInformation.instrumentIdentifier.id

field instead of the card number.