Use the /simulateCardAuth endpoint to simulate a card authorization in non-production environments. This endpoint creates but does not settle a card authorization for the account.
📘 Note: This endpoint is only available in non-production environments (local, development, sandbox, cv). Calls to this endpoint in production will return an error.
Requirements:
- The account must be active
- For debit accounts, sufficient balance is required
- Card blocks must be set to 'none' on the account
Result:
When successfully called, this endpoint returns an authId that can be used with Simulate Card Settle to complete the transaction.
Choosing the simulation path (useAttachedCardNetwork):
useAttachedCardNetwork):Some accounts have a card network (Galileo) attached on top of a different primary system of record — for example, a LoanPro-backed line of credit with an attached Galileo card. For those accounts there are two distinct paths that can produce a transaction, and this flag controls which one the simulation exercises:
- Card network path — the simulation is run against the attached card network (Galileo). This mirrors what happens in production when a real card swipe is authorized by the network and then forwarded to the primary system.
- Primary path — the simulation is run directly against the account's primary vendor (e.g., LoanPro for an LMS-backed account), bypassing the card network. Useful for testing the system-of-record's behavior in isolation.
Behavior by value:
- Omitted (default) — runs on the attached card network when one is present on the account; otherwise runs on the account's primary vendor. For native Galileo accounts (where Galileo is also the primary vendor), this is always Galileo.
true— forces the attached card network path. Returns a400 ATTACHED_CARD_NETWORK_NOT_FOUNDerror if the account has no attached card network.false— forces the account's primary path, even if a card network is attached. For a LoanPro-backed account this routes the simulation to the LMS side.
For native Galileo accounts (no separate primary vendor), all three values resolve to the same Galileo simulation.