This creates a new authorization based on information from a previous transaction. This is useful if you do not want to resubmit credit card information or if your processor does not support Auth Reversals. The original orderID is required.

Transaction Administration - Authorize Previous

Overview

The Authorize Previous operation allows a new authorization to be created using data from a prior transaction, excluding the original amount. This reduces the need to resubmit full billing information by referencing an existing transaction.

Request Parameters

Variable Requirement Type Max Size Possible Values / Example Description Notes
publisher-name Mandatory string N/A Example: gatewayuser Gateway account username issued to you.
publisher-password Mandatory string N/A Example: securepassword Remote Client Password for API authentication. This differs from the password used to log in to the admin interface.
mode Mandatory string N/A authprev Defines the transaction operation type. Must be set to authprev.
origorderid Mandatory string N/A Example: 1234567890 Original transaction ID, that was Cardholder Initiated Original transaction in which the cardholder gave permission to store card data for future use.
prevorderid Mandatory string 20 Example: 1234567890 Related transaction ID used as the reference for this authorization. Billing data is only valid for 2 years from the original transaction date. Only the most recent order ID should be retained for reuse.
card-amount Mandatory decimal 10 1234.56 Amount to be authorized for the new transaction. 1 Must be formatted as a standard decimal value.
currency Optional / Mandatory string 3 USD ISO 3-character currency code. Used with card-amount. Defaults to USD; required for multicurrency accounts.
transflags Optional string N/A recurring, debt, multicurrency, avsonly, fleet, cit, mit Defines special processing instructions for the transaction. See allowed values below. Card on File values (cit, mit, and combinations) are documented separately.

transflags Allowed Values

  • recurring – Marks transaction as recurring billing (not for initial signup)
  • debt – Indicates Visa debt repayment transaction (TSYS processors only)
  • multicurrency – Enables multi-currency processing for supported gateways
  • avsonly – Performs address verification only; allows 0.00 amount transactions
  • fleet – Indicates Petroleum Fleet Card usage (fleet merchants only)
  • cit / mit – Card on File indicators for cardholder-initiated or merchant-initiated stored credential transactions; see Card On File Requirements

Response Parameters

Variable Value Description Notes
FinalStatus success, problem, pending Indicates overall processing outcome. Some processors may return pending before final settlement.
success yes, no Indicates whether the request was successful. Mirrors transaction outcome status.
aux-msg string Informational success message returned by the gateway. Example: order marked for settlement.
MErrMsg string Error message returned when the transaction fails. Example: missing or invalid previous order ID.

Notes

  • Only live transactions under 2 years old may be used with authprev.
  • Test transactions and expired records are not valid for this operation.
  • It is recommended to always store and update the most recent valid prevorderid to avoid failures.
  • Ensure transaction reuse aligns with card storage and compliance requirements.

⚠️ Formatting Rule (Applies to All Amount Fields)

  1. All monetary values must be numeric only in the format 1234.56. Do not include currency symbols, commas, or formatting. Exactly two decimal places are required. ↩︎