Mass Transit Payment Services Using EMV and Card Data
You can request these payment services for mass transit with EMV and card data:
- Authorization for account verification and debt recovery
- Sale for aggregated fares and debt recovery
- Stand-alone credit
This table shows which EMV tags are:
- M: mandatory
- P: prohibited
- O: optional
- C: conditional (Send the tag when it is present in card and terminal.)
Data Element | EMV Tag | American Express | Mastercard PAYG | Visa MTT |
---|---|---|---|---|
Transaction Date | 9A | M | M | M |
Transaction Type | 9C | M | M | M |
Transaction Currency Code | 5F2A | M | M | M |
Terminal Country Code | 9F1A | M | M | M |
Amount Authorized | 9F02 | M | M | M |
Amount Other | 9F03 | M | M | M |
Application PAN Sequence Number | 5F34 | M | C | O |
Application Transaction Counter (ATC) | 9F36 | M | M | M |
Application Interchange Profile (AIP) | 82 | M | M | M |
Dedicated File (DF) Name | 84 | M | M | M |
Terminal Verification Results (TVR) | 95 | M | M | M |
Issuer Application Data | 9F10 | M | M | M |
Application Cryptogram | 9F26 | M | M | M |
Cryptogram Information Data (CID) | 9F27 | M | M | O |
Terminal Capabilities | 9F33 | M | M | M |
Cardholder Verification Method (CVM) Results | 9F34 | O | M | O |
Unpredictable Number (UN) | 9F37 | M | M | M |
Form Factor Indicator | 9F6E | C* | O (Authorizations) P (Refunds) | C |
Mastercard Authenticated Application Data | 9F60 | Does not apply | O | Does not apply |
Mastercard Kernel Identifier‐Terminal | 96 | Does not apply | O | Does not apply |
*For contactless American Express transactions, if the form factor
indicator data is available on the card, the merchant, acquirer, or processor must forward this information to the issuer.
Transaction Types
When you include the transaction type in your request, the description appears in the
Business Center
and transaction reports.
Transactions are grouped into these categories:
-
TransitDA: deferred-aggregated (DA) transactions, which are also known asVisa MTTandMastercard PAYGtransactions.
-
BAU: business-as-usual transactions that represent no exceptions or errors for cardholders.
-
FRR: first-ride-risk transactions that occur where first-ride-risk liability shift is being operated. These are specific to a card scheme and region.
-
DR: debt-recovery transactions initiated by the merchant or when the cardholder taps a contactless card at a validator to enter the transit system.
-
DR CIT: debt-recovery transactions initiated by the cardholder when they explicitly pay a debt, including e-commerce and telephone orders.
-
Service: standard transactions for completing a payment.
-
Error: standard transactions for handling transaction errors.
To include the transaction type, set the
clientReferenceInformation.comments
request field to the transaction value corresponding to the service description. These tables provide the value for each type of transaction:
Service
|
Field Value
|
Description
|
---|---|---|
authorization
|
TransitDA BAU zero value auth
|
Zero amount authorization to verify a card.
|
authorization
|
TransitDA BAU nominal value auth
|
Nominal value authorization to verify a card.
|
authorization
|
TransitDA BAU full value auth
|
Deferred aggregated authorization for the aggregated value that is sent at the end of the travel period.
|
sale
|
TransitDA BAU full value sale
|
Deferred aggregated authorization and capture for the aggregated value that is sent at the end of the travel period.
|
capture
|
TransitDA BAU capture
|
Capture of any business as usual authorization. Could be a nominal authorization or full value authorization.
|
capture
|
TransitDA BAU capture (split)
|
Capture without a previous authorization. Used by Mastercard PAYG in the UK.
|
authorization
|
TransitDA BAU registration auth
|
Zero amount authorization as part of journey history service. Could include CVV2 and 3-D Secure 2.x.
|
Service
|
Field Value
|
Description
|
---|---|---|
authorization
|
TransitDA FRR full auth
|
Full amount authorization for a previous verification authorization request that was declined. Decline response is common.
|
capture
|
TransitDA FRR capture
|
Forced capture of a declined authorization when FRR funding applies.
|
authorization
|
TransitDA FRR MIT DR auth
|
Merchant-initiated authorization to clear a debt status after the TransitDA FRR capture is processed. If successful, the FRR capture is reversed.
|
reversal
|
TransitDA FRR MIT DR reversal
|
Reversal sent if previous TransitDA FRR MIT DR auth was successful.
|
authorization
|
TransitDA FRR tap DR auth
|
Authorization sent following a card tap to clear a debt status after TransitDA FRR capture is processed. If successful, the FRR capture is reversed.
|
reversal
|
TransitDA FRR tap DR reversal
|
Reversal when a TransitDA FRR tap DR auth was successful.
|
Service
|
Field Value
|
Description
|
---|---|---|
sale
|
TransitDA Debt recovery MIT sale FPAN
TransitDA Debt recovery MIT sale DPAN
|
Merchant-initiated debt recovery authorization and capture using a funding PAN (FPAN) or digital PAN (DPAN).
|
authorization
|
TransitDA Debt recovery MIT auth FPAN
TransitDA Debt recovery MIT auth DPAN
|
Merchant-initiated debt recovery authorization using a funding PAN (FPAN) or digital PAN (DPAN).
|
capture
|
TransitDA Debt recovery MIT capture
|
Merchant-initiated debt recovery capture of a previous TransitDA Debt recovery MIT auth transaction.
|
sale
|
TransitDA Debt recovery tap sale
|
Tap-initiated EMV debt recovery authorization and capture.
|
authorization
|
TransitDA Debt recovery tap auth
|
Tap-initiated EMV debt recovery authorization.
|
capture
|
TransitDA Debt recovery tap capture
|
Tap-initiated EMV debt recovery capture of a previous TransitDA Debt recovery tap auth transaction.
|
Service
|
Field Value
|
Description
|
---|---|---|
sale
|
TransitDA Debt recovery CIT Ecom sale
|
Cardholder-initiated debt recovery authorization and capture.
|
authorization
|
TransitDA Debt recovery CIT Ecom auth
|
Cardholder-initiated debt recovery authorization.
|
capture
|
TransitDA Debt recovery CIT Ecom capture
|
Cardholder-initiated debt recovery capture of a previous TransitDA Debt recovery CIT Ecom auth transaction.
|
sale
|
TransitDA Debt recovery CIT Ecom 3DS2 sale
|
Cardholder-initiated debt recovery authorization and capture.
|
authorization
|
TransitDA Debt recovery CIT Ecom 3DS2 auth
|
Cardholder-initiated debt recovery authorization.
|
capture
|
TransitDA Debt recovery CIT Ecom 3DS2 capture
|
Cardholder-initiated debt recovery capture of a previous TransitDA Debt recovery CIT Ecom 3DS2 auth transaction.
|
sale
|
TransitDA Debt recovery CIT Moto sale
|
Cardholder-initiated debt recovery authorization and capture.
|
authorization
|
TransitDA Debt recovery CIT Moto auth
|
Cardholder-initiated debt recovery authorization.
|
capture
|
TransitDA Debt recovery CIT Moto capture
|
Cardholder-initiated debt recovery capture of previous TransitDA Debt recovery CIT Moto auth transaction.
|
Service
|
Field Value
|
Description
|
---|---|---|
refund
|
REFUND Automatic
|
Programmatic follow-on refund for a previous capture.
|
credit
|
CREDIT Automatic
|
Programmatic stand-alone credit.
|
refund
|
REFUND Manual
|
Manual follow-on refund for a previous capture.
|
credit
|
CREDIT Manual
|
Manual stand-alone credit.
|
Service
|
Field Value
|
Description
|
---|---|---|
reversal
|
REVERSAL Timeout
|
Reversal of a previous request for which a response was not received.
|
reversal
|
REVERSAL other
|
Reversal for an authorization for a reason other than TransitDA FRR MIT DR reversal, TransitDA FRR tap DR reversal, or REVERSAL Timeout.
|
void
|
VOID Timeout
|
Void of a previous request for which a response was not received.
|
void
|
VOID Payment
|
Void of a payment within the same day.
|
void
|
VOID Capture
|
Void of a capture within the same day.
|
void
|
VOID Refund
|
Void of a refund within the same day.
|
void
|
VOID Credit
|
Void of a credit within the same day.
|
Required Fields for Authorizations with EMV Data
This table provides information about the fields required to process authorizations with EMV data.
REST API Field
|
American Express Account Status Check
|
American Express Delayed Online
|
Mastercard PAYG
|
Visa MTT
|
Information/Value
|
---|---|---|---|---|---|
|
|
|
|
—
|
|
|
|
|
|
For this value, see Transaction Types.
|
|
|
|
|
|
Cybersource
provides the value for this field.
|
|
|
|
|
|
Cybersource
provides the value for this field.
|
|
|
|
|
|
—
|
|
|
|
|
|
—
|
|
|
|
|
|
For Visa AVR, set this field to
0.00
.
|
|
|
|
|
|
—
|
|
—
|
—
|
|
—
|
—
|
|
|
|
|
|
Set this field to
2
.
|
|
|
|
—
|
|
For Visa, set this field to
1
.
|
|
|
|
|
|
—
|
|
|
|
|
|
Set this field to
contactless
.
|
|
—
|
—
|
|
—
|
—
|
|
|
|
|
|
Set this field to
5
.
|
|
|
|
|
|
—
|
|
|
|
|
|
Set this field to
0
.
|
|
|
|
|
|
—
|
|
|
—
|
|
—
|
Set this field to
true
.
|
|
—
|
—
|
|
—
|
Set this field to
0
.
|
|
|
—
|
|
—
|
Set this field to
true
.
|
|
—
|
—
|
|
—
|
—
|
|
|
|
|
—
|
—
|
|
|
|
|
|
Set this field to
retail
.
|
|
|
|
|
—
|
Set this field to
transit
.
|
American Express Authorization with EMV Data
An American Express authorization with EMV data is an authorization request for a nominal amount of 1.00 USD or more. These two models are supported for American Express:
-
Account status check (Required function code to be 190)
-
Delayed online authorization (Required function code to be 100)
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Mastercard Authorization with EMV Data
A Mastercard authorization with EMV data is an authorization request for a nominal amount.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Visa Account Verification Request (AVR) with EMV Data
A Visa account verification request (AVR) with EMV data is a zero amount authorization.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Required Fields for Sales with EMV Data
This table provides information about the fields required for sales with EMV data.
REST API Field
|
Visa Deferred
|
Information/Value
|
---|---|---|
|
—
|
|
|
For this value, see Transaction Types.
|
|
|
—
|
|
|
Cybersource
provides the value for this field.
|
|
|
Cybersource
provides the value for this field.
|
|
|
—
|
|
|
—
|
|
|
For Visa AVR, set this field to
0.00
.
|
|
|
—
|
|
|
Set this field to
2
.
|
|
|
—
|
|
|
—
|
|
|
Set this field to
contactless
.
|
|
|
Set this field to
5
.
|
|
|
—
|
|
|
Set this field to
0
.
|
|
|
—
|
|
|
Set this field to
true
.
|
|
|
Set this field to
true
.
|
|
|
Set this field to
true
.
|
|
|
—
|
|
|
Set this field to
transit
.
|
Visa Deferred Sale with EMV Data
A sale transaction is a bundled authorization and capture. At the end of the travel period, request a Visa deferred sale with EMV data for an aggregated payment.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Required Fields for Authorization for Debt Recovery
This table provides information about the fields required for tap-initiated and merchant-initiated (MIT) authorizations for debt recovery.
REST API Field
|
Tap
|
MIT
|
Information/Value
|
---|---|---|---|
|
|
—
|
|
|
|
For this value, see Transaction Types.
|
|
|
|
Cybersource
provides the value for this field.
|
|
|
|
Cybersource
provides the value for this field.
|
|
|
|
—
|
|
|
|
—
|
|
|
|
—
|
|
—
|
|
—
|
|
—
|
|
—
|
|
—
|
|
—
|
|
|
|
—
|
|
|
|
Set this field to
2
.
|
|
|
—
|
Set this field to
1
.
|
|
|
—
|
—
|
|
|
—
|
Set this field to
contactless
.
|
|
|
—
|
Set this field to
5
.
|
|
|
—
|
—
|
|
|
—
|
Set this field to
0
.
|
|
|
—
|
—
|
|
|
|
Set this field to
true
.
|
|
|
—
|
Set this field to
true
.
|
|
—
|
|
Set this field to
true
.
|
|
—
|
|
Set this field to
true
.
|
|
—
|
|
Set this field to
false
.
|
|
—
|
|
—
|
|
—
|
|
Set this field to
1
.
|
|
—
|
|
Set this field to
true
.
|
|
—
|
|
Set this field to
merchant
.
|
|
|
—
|
—
|
|
|
|
Set this field to
retail
.
|
|
|
|
Set this field to
transit
.
|
Tap-Initiated Authorization for Debt Recovery with EMV Data
When a cardholder attempts to use a blocked card at the transit reader, create a new debt recovery authorization request using the chip data from the new tap, along with the fare amount of the previous declined authorization.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Merchant-Initiated Authorizations for Debt Recovery with Stored Card Data
You can request the authorization service for a merchant-initiated debt recovery with stored card data.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Required Fields for Sales for Debt Recovery
This table provides information about the fields required for tap-initiated and merchant-initiated (MIT) sales for debt recovery.
REST API Field
|
Tap
|
MIT
|
Information/Value
|
---|---|---|---|
|
|
—
|
|
|
|
For this value, see Transaction Types.
|
|
|
|
Cybersource
provides the value for this field.
|
|
|
|
Cybersource
provides the value for this field.
|
|
|
|
—
|
|
|
|
—
|
|
|
|
—
|
|
—
|
|
—
|
|
—
|
|
—
|
|
—
|
|
—
|
|
|
|
—
|
|
|
—
|
Set this field to
00
.
|
|
|
—
|
Set this field to
2
.
|
|
|
—
|
—
|
|
|
—
|
Set this field to
contactless
.
|
|
|
—
|
—
|
|
|
—
|
Set this field to
5
.
|
|
|
—
|
—
|
|
|
—
|
Set this field to
0
.
|
|
|
—
|
—
|
|
|
|
Set this field to
1
.
|
|
|
|
Set this field to
true
.
|
|
|
—
|
Set this field to
true
.
Do not include for Mastercard transactions.
|
|
—
|
|
Set this field to
true
.
|
|
—
|
|
Set this field to
true
.
|
|
—
|
|
—
|
|
—
|
|
Set this field to
1
.
|
|
—
|
|
Set this field to
true
.
|
|
—
|
|
Set this field to
merchant
.
|
|
|
|
—
|
|
|
|
Set this field to
true
.
|
|
|
|
—
|
|
|
|
For tap-initiated, set this field to
retail
.
For merchant-initiated, set this field to
moto
.
|
|
|
|
Set this field to
transit
.
|
Tap-Initiated Sales for Debt Recovery with EMV Data
A sale transaction is a bundled authorization and capture. When a cardholder attempts to use a blocked card at the transit reader, create a fresh debt recovery sale request using the chip data from the new tap, along with the fare amount of the previous declined authorization.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Merchant-Initiated Sales for Debt Recovery with Stored Card Data
Request a bundled authorization and capture to perform a merchant-initiated sale for debt recovery.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/payments
Test:
POST
https://apitest.cybersource.com
/pts/v2/payments
Required Fields for Stand-Alone Credits with Card Data
This table provides information about the fields required to process stand-alone credits with card data.
REST API Field
|
Stand-Alone
|
Information/Value
|
---|---|---|
|
—
|
|
|
For this value, see Transaction Types.
|
|
|
Cybersource
provides the value for this field.
|
|
|
Cybersource
provides the value for this field.
|
|
|
—
|
|
|
—
|
|
|
—
|
|
|
—
|
|
|
—
|
|
|
—
|
|
|
—
|
Stand-Alone Credits with Card Data
WARNING
Follow these guidelines to prevent unauthorized credits.
A
stand-alone credit
is a credit that is not linked to a capture. There is no time limit for requesting a stand-alone credit.
When a request for a credit is successful, the issuing bank for the payment card takes money out of your merchant bank account and returns it to the customer. It usually takes two to four days for your acquiring bank to transfer funds from your merchant bank account.
Carefully control access to the credit service. Do not request this service directly from your customer interface. Instead, incorporate this service as part of your customer service process.
Endpoint
Production:
POST
https://api.cybersource.com
/pts/v2/credits/
Test:
POST
https://apitest.cybersource.com
/pts/v2/credits/