transactionIntent
The transactionIntent property is used to identify the intent of the authorization requests. The value of the transactionIntent shows if the transaction is crypto or quasi-cash related one.
-
It is an optional enum field applicable for every MCC.
-
It is required only if the use cases explained below are applicable for the merchants or the default behavior is not acceptable for them.
-
The merchant needs to add in the request transactionIntent property value as shown in the example below.
Use cases and applicable valid enum transactionIntent options:
| Use case | MCC | Valid transactionIntent value |
|---|---|---|
| The consumer is acquiring cryptocurrency in a transaction. | 6012, 6051 | CRYPTO_ON_RAMP |
| The consumer is loading a cryptocurrency wallet or exchange account with fiat. *Applicable only in combination with valid fundingTransaction object. | 6012, 6051 | WALLET_CRYPTO_ON_RAMP |
| The consumer is acquiring quasi-cash in a transaction. *Quasi cash transactions represent the purchase of foreign currencies or items (including, but not limited to, casino chips, money orders, lottery tickets and travelers cheques) which may be convertible to cash. | 4829, 6012, 6051 | QUASI_CASH |
| For purchases of goods or services that leverage a live conversion of fiat into non - fiat currency. | ANY | BUY_WITH_CRYPTO |
Default transactionIntent definition by Paysafe
-
All authorizations processed by MCC 6051 will be classified as crypto related with transactionIntent "CRYPTO_ON_RAMP" or "WALLET_CRYPTO_ON_RAMP" (when funding a wallet), except their account is not configured by Paysafe for quasi-cash transactions.
-
All authorizations processed by MCC 6051 will be classified as crypto related with transactionIntent "CRYPTO_ON_RAMP" or "WALLET_CRYPTO_ON_RAMP" (when funding a wallet), except their account is not configured by Paysafe for quasi-cash transactions.All authorizations processed by MCC 6051 or 4829 with quasi-cash configuration turned on will be classified as quasi-cash related with transactionIntent "QUASI_CASH" .
Expected errors related to invalid transactioIntent values:
-
If you send transactionIntent type in the authorization request with value not applicable for your MCC, the transaction will be declined with error 3072 - "Your request has been declined because the requested transactionIntent value is not applicable for your merchant category code (MCC)".
-
If you send transactionIntent type WALLET_CRYPTO_ON_RAMP in the authorization request, but you didn't classify the transaction as "funding" one with the respective valid fundingTransaction object, the transaction will be declined with error 3071 - Your request has been declined because of mismatch between the requested transactionIntent and fundingTransaction type.
Note: More about the usage of transactionIntent in standalone credit request can be found here DRAFT - Transaction intent field in standalone credits - Technical documentation for merchant's comms (dev center address to be added).
Possible values: [CRYPTO_ON_RAMP, WALLET_CRYPTO_ON_RAMP, QUASI_CASH, BUY_WITH_CRYPTO]
{
"transactionIntent": "CRYPTO_ON_RAMP"
}