Using Customer Information Management profiles, my customers process Standing Instruction Merchant Initiated Transactions for varying amounts every 28 or 30 days for theiir accounts. The descriptions given for the reason codes: (reauthorization, resubmission, delayed charge, no show) do not seem to fit these transactions. What reason code should be used?
05-05-2021 01:17 PM
None. This would be a recurring payment.
https://developer.authorize.net/api/reference/features/card-on-file.html
05-05-2021 04:12 PM
@kabutotx wrote:None. This would be a recurring payment. five nights at freddy's
https://developer.authorize.net/api/reference/features/card-on-file.html
Thank you! This helps.
05-11-2021 12:16 AM
Actually, its not a recurring payment.
I probably wasn't clear explaining the scenario,
By definition it's an CIM MIT UnScheduled COF Payment because the customer is charged with their agreement at varying times for varying amounts.
My question is what reason code should be used for a
createTransactionRequest api call?
Example given is resubmission.
Definition for resubmission does not "fit":
"Resubmission
If the follow-on MIT transaction is due to a decline, and when the products or services have been provided to the customer:
Under the subesquentAuthInformation element, set reason to resubmission.'"
e.g.
{ "createTransactionRequest": {
"merchantAuthentication": {
"name": "9bSaKC66uHg",
"transactionKey": "8xszx7B7674QxHqe"
},
"refId": "123456",
"transactionRequest": {
"transactionType": "authCaptureTransaction",
"amount": "45",
"profile": {
"customerProfileId": "40338125",
"paymentProfile": {
"paymentProfileId": "1000177237" }
},
"processingOptions": {
"isSubsequentAuth": "true"
},
"subsequentAuthInformation": {
"originalNetworkTransId": "123456789123456",
"originalAuthAmount": "45.00",
"reason": "resubmission"
},
"authorizationIndicatorType": {
"authorizationIndicator": "final"
}
}
}
05-14-2021 07:43 AM
No reason is needed for Unscheduled COF.
05-14-2021 09:19 AM