Making a One-Time Transaction

You can perform two types of one-time transaction in E-Pay:

One-time payment
One-time credit
Certain business rules apply when working with real-time E-Pay transactions.

Business rules set up for working with Shift4 are as follows.

Only transactions with a status of "Unprocessed One Time" are processed. Real-time statuses of "Unprocessed" transactions are changed to "Unprocessed One Time" before transmission of the record if set up to do so in the InfoScript of this event.
Transactions with a future process date are not sent real-time. They are sent at the scheduled time for batch processes.
Debit transactions are sent as Sales types (ID = S).
Credit transactions are sent as Credit types (ID = C).
An Adjustment is created for approved credit transactions
A Payment is created for approved charge (debit) transactions.
The system checks for duplicate payments and adjustments
Void transactions are sent as Void types (ID= 08).
If the void transaction fails, the error information is stored for that transaction.
The unposted payment that is associated with the void transaction is deleted.
If a connection cannot be made to void a transaction, the transaction is voided and a follow-up is sent to the user indicating that the void failed and that it should be completed manually on the Shift4 Web site.

Business rules set up for working with Authorize.NET are as follows.

Only transactions with a status of "Unprocessed One Time" are processed.
Transactions with a future process date are not sent real-time. They are sent at the scheduled time for batch processes.
Credit (charge) transactions are sent as AUTH_CAPTURE types.
Credit transactions are sent as Credit types (ID = CREDIT).
An Adjustment is created for approved credit transactions
A Payment is created for approved charge (debit) transactions.
Void transactions are sent as Void types (ID = VOID).
If the void transaction fails, the error information is stored for that transaction.
The unposted payment that is associated with the void transaction is deleted.
If a connection cannot be made to void a transaction, the transaction is voided and a follow-up is sent to the user indicating that the void failed and that it should be completed manually on the Authorize.Net Web site.