Transaction Initiator Indicator (CIT and MIT)
Valid only for Mastercard and Hipercard.
The following tables apply to Mastercard credit and debit transactions with stored credentials. The objective is to identify whether the transaction was initiated by the cardholder or by the merchant:
- Cardholder-Initiated Transaction (CIT): the transaction is initiated by the cardholder, who provides their payment credentials and allows them to be stored.
- Merchant-Initiated Transaction (MIT): the transaction is initiated by the merchant, after an agreement in which the cardholder authorizes the merchant to save and use the account data to initiate one or more transactions in the future (such as recurrent payments or installments, and charges commonly applied by the tourism and hospitality sector).
The transaction initiator indicator must be sent in the node Payment.InitiatedTransactionIndicator, within parameters Category and Subcategory. Please refer to the following request example and tables for more information:
Please refer to the API Reference for complete request and response for the desired payment method:
What to send in the request
| Environment | Method | Endpoint |
|---|---|---|
| Sandbox | post | https://apisandbox.braspag.com.br/v2/sales/ |
| Production | post | https://api.braspag.com.br/v2/sales/ |
"Payment":{
(...)
"InitiatedTransactionIndicator": {
"Category": "C1",
"Subcategory": "Standingorder"
},
(...)
}
| Property | Type | Size | Required | Description |
|---|---|---|---|---|
Payment.InitiatedTransactionIndicator.Category | string | 2 | Conditional. Required only for Mastercard and Hipercard. | Transaction Initiator Indicator category. Valid only for Mastercard. Possible values: - “C1”: transaction initiated by the cardholder; - “M1”: recurring payment or installment initiated by the merchant - “M2”: transaction initiated by the merchant. |
Payment.InitiatedTransactionIndicator.Subcategory | string | - | Conditional. Required only for Mastercard and Hipercard. | Transaction Initiator Indicator subcategory. Valid only for Mastercard and Hipercard. Please refer to the Transaction Initiator Indicator tables for the full list. |
What the response will return
The response will be the default response for the credit or debit transaction, returning the node Payment.InitiatedTransactionIndicator as sent in the request.
Transaction initiator tables
CIT and MIT categories
The categories (C1, M1 or M2) must be sent in parameter Payment.InitiatedTransactionIndicator.Category.
| Category | Transaction initiator | Description |
|---|---|---|
C1 | Cardholder-initiated transaction (CIT). | The transaction is initiated by the cardholder. The cardholder provides card data and agrees with the merchant storing payment credentials or makes a purchase using previously stored payment credentials. The subcategory will indicate the reason for the purchase or for storing card data. |
M1 | Merchant-initiated transaction (MIT). | The merchant has stored the payment credentials in the past (tokenized and with cardholder consent) and is authorized to initiate one or more transactions in the future for recurrent payments or installments. |
M2 | Merchant-initiated transaction (MIT). | The merchant has stored the payment credentials in the past (tokenized and with cardholder consent) and is authorized to initiate one or more transactions in the future in order to charge for partial deliveries, related/delayed expenses, no-show fees and retry/resubmission. |
CIT and MIT subcategories
The subcategories must be sent in parameter Payment.InitiatedTransactionIndicator.Subcategory.
| Initiator category | Initiator subcategory | Meaning | Example |
|---|---|---|---|
C1 | CredentialsOnFile | Cardholder-initiated transaction in which the cardholder provides card data and agrees with the merchant storing payment credentials or makes a purchase using previously stored payment credentials. | The cardholder initiates the purchase and the merchant is authorized to save card data for future purchases initiated by the cardholder, such as one-click-buy. |
C1 | StandingOrder | Cardholder-initiated transaction in which the cardholder provides card data and agrees with the merchant storing payment credentials for future payments of fixed amount and variable frequency. | Initial transaction to store card data for utility bills monthly payments. |
C1 | Subscription | Cardholder-initiated transaction in which the cardholder provides card data and agrees with the merchant storing payment credentials for recurrent payments of fixed amount and frequency. | Initial transaction to store card data for a monthly subscription (e.g .newspapers and magazines). |
C1 | Installment | Cardholder-initiated transaction in which the cardholder initiates the first installment and authorizes the merchant to save card data for the next installments. | Initial transaction to store card data for installment buying |
M1 | CredentialsOnFile | Merchant-initiated unscheduled transaction of fixed or variable amount. | When the cardholder agrees with transactions for toll charges when the balance in their account is below a certain amount (auto-recharge). |
M1 | StandingOrder | Merchant-initiated transaction of variable amount and fixed frequency. | Utility bills monthy payments. |
M1 | Subscription | Merchant-initiated transaction of fixed amount and fixed frequency. | Monthly subscription or fixed monthly service payment. |
M1 | Installment | Merchant-initiated transaction of known amount and defined period. | If a shopper buys a TV for $600 and chooses to pay in three $200 installments; in this situation, the first transaction is initiated by the cardholder and the following two transactions are initiated by the merchant. |
M2 | PartialShipment | Merchant-initiated transaction when the order will be delivered in more than one shipping. | Partial shipment may occur when the amount of purchased goods in the e-commerce is not available for shipping in the time of purchase. Each shipping is a separate transaction. |
M2 | RelatedOrDelayedCharge | Merchant-initiated transaction for additional expenses, i.e., additional charges after providing initial services and processing the payment. | A hotel minibar fridge charges after cardholder check-out. |
M2 | NoShow | Merchant-initiated transaction for no-show charges according to the merchant cancellation policy. | The cancellation of a reservation by the cardholder without adequate prior notice to the merchant. |
M2 | Resubmission | Merchant-initiated transaction for retrying previously denied transactions. | The previous attempt to submit a transaction was denied, but the issuer response does not prohibit the merchant to retry, such as insufficient funds/response above credit limit. |
Card data is stored in encrypted format (tokenized).