Use the /simulateCardSettle endpoint to settle a simulated card authorization that was created via Simulate Card Auth.

📘 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 authId must be from a valid pending authorization
• The account must be active

Result:

When successfully called, the authorization is settled and the account balance is updated accordingly.

Choosing the simulation path (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 a 400 ATTACHED_CARD_NETWORK_NOT_FOUND error 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.

Important: the value passed here must match the value used on the originating Simulate Card Auth call. Settling on a different path than the auth was created on will fail to find the pending authorization.