Objects MIT object
The mit object is important for MIT (Merchant-Initiated Transactions). If you do consider processing the credit card payments over Direct API on customer’s behalf, include this object into your Direct API requests.
STRUCTURE
✓ - required value
? - optional, value or null
✕ - always appears as null
| Variable | Type | 0-Auth | MIT Initial | MIT Subsequent | Description |
|---|---|---|---|---|---|
| type | varchar(32) | ✓ | ✓ | ✓ | Type of MIT transaction. Possible values: - initial - subsequent Required field for every MIT attempts |
| expiry | int(5) | ✓ | ✓ | ? | Time to expire the transaction in days. After expiration, the system will not allow to process subsequent MIT using this transaction. Optional, default value is 365 (1 year). |
| mit_reference_id | int(11) | ✕ | ✕ | ✓ | TID from previous successful zero-authorization or initial-mit transactions. Required for subsequent MIT requests. |
{danger.fa-exclamation-triangle} Please note: all the parameters within the mit object will be sent in CRM Notification, despite the transaction is Initial or Subsequent. The difference in mit_expiry will be null for Subsequent and mit_reference_id will be null for Initial.
EXAMPLE
MIT Initial Sale
{
"transaction_type": "sale",
"mit":{
"type":"initial",
"expiry":365
}
}MIT Subsequent Sale
{
"transaction_type": "sale",
"mit":{
"type":"subsequent",
"mit_reference_id":"TID from mit-initial transaction"
}
}