Home / Issuing / Handle Transactions

Simulate Transactions


This guide can be used for any Card Product, with the exception of Visa Fleet Card Products. To simulate transactions for Visa Fleet Card Products, see Simulate Fleet Transactions.

  1. Review Transaction Lifecycle
  2. A Highnote Account
  3. An API Key, the API Explorer, or the Dashboard
  4. A Card Product, Financial Account, and Payment Card


Warning: The Highnote test environment allows you to freely explore the platform features and functionality. It is intended for experimenting, building integrations, and training your team.

To ensure the security of your real-world data, please refrain from entering production data into the test environment. Production data includes sensitive information like customer details, financial data, or personally identifiable information (PII).

Use only dummy or test data explicitly created for testing purposes in the test environment.

You can simulate Transactions to test different merchant types, transaction amounts, and Account Holders making purchases in other countries. This simulation allows you to test Authorization Controls, including:

  • Spend Rules
  • Velocity Controls
  • Collaborative Authorization

Simulated authorizations use the same logic as authorizations from card networks such as Mastercard and Visa. Authorizations may be approved or declined based on several factors. See the API Reference for a full list of Response Codes to assist your communications with your Account Holders.

Use the following mutation to simulate Authorization in your Test Environment:


Clearing happens alongside authorizations, or in batches after an authorization is approved. After a transaction clears, the money is removed from the Account Holder's Financial Account.

Use the following mutation to simulate clearing. You can try capturing transactions for amounts under and over the original authorization amount:

Authorization and Clearing

Some transactions authenticated with a PIN execute authorization and clearing in a single message. This allows for an AUTH AND CLEAR event. This process eliminates batch processing.

Use the following mutation to simulate an AUTH AND CLEAR event:


When an authorization has not cleared yet, it can be reversed. Reversing an authorization makes the funds available to the Account Holder again. This scenario is helpful when a Account Holder places an order, one of the items is out of stock, and the original authorization needs to be reduced.

Use the following mutation to simulate a Reversal:


You cannot simulate refunds that are not linked to a previous transaction.

Refunds can be simulated for transactions that are cleared. You can refund the total or partial amount of the original transaction. Simulating a refund results in a new transaction with its own id and transactionEvents.

When you call the simulateRefund mutation, you will receive a ClearingEvent in response. Use the following mutation to simulate a Refund:

Provide Feedback

Was this content helpful?