What happens if I don't disable the transaction testing function before going live?

You can experience inconsistent data between applications. You may also unintentionally create holds or charges on credit cards for amounts not owed by the cardholder.

Use the transaction testing functionality to initiate transactions without source product interaction to test the setup of Oracle Fusion Payments and the payment system connectivity. Transactions initiated from Payments, rather than the source product, aren't recorded in any source product. This functionality is a valuable testing and diagnostic tool, but it can create inconsistent data between applications if used incorrectly in an active environment.

Caution: On an active instance of Payments, Oracle strongly recommends that you disable the transaction testing functionality and unassign it from the payment administrator.