Create Simulated Card Settlement

Use the Create Simulated Card Settlement endpoint to settle a simulated card authorization in the CV environment. First, create a simulated authorization using the Create Simulated Card Authorization endpoint, and then use this endpoint to settle it.

  • If authId is not populated, then merchantName is required. Populate merchantName but not authId to simulate a force-posted transaction.
  • For instructions on using this endpoint see Simulating Card Transactions.

🚧

Warning

This endpoint does not support XML responses. If you pass response-content-type: xml, it will be ignored.

🚧

Warning

Do not use this endpoint in Production.

Status codes

See Global Response Statuses for status codes that are common across endpoints.

The table below lists status codes that apply to this specific endpoint.

Status codeDescription
544-01Method not available in the production environment
544-02Authorization is not found for account
544-03Authorization is already settled or in the wrong status
Form Data
string
required

Web service username, as provided by Galileo.
Pattern: Max 50 characters
Example: "AbC123-9999"

string
required

Web service password, as provided by Galileo.
Pattern: Max 15 characters
Example: "4sb62fh6w4h7w34g"

integer
required

Galileo-issued provider identifier.
Pattern: Max 10 digits
Example: 9999

integer
required

A unique provider-generated ID to identify this API call. A UUID is preferred.
Pattern: 60 characters or less
Example: "9845dk-39fdk3fj3-4483483478"

string
required

The PRN or PAN of the account.
Pattern: PAN or PRN
Example: "074103447228"

number
required

The amount of the transaction in the currency at the point of sale.
Pattern: Positive integer or decimal number
Example: 100.00, 100, or 100.73

string
required

Specifies which card network to simulate: visa (Visa) or mc_auth (Mastercard).
Pattern: string
Example: "visa"

string
required

Simulated merchant name. Pass 40 characters for the complete string or pass up to 22 characters and the simulator will add 18 characters of a simulated address. For settlements, this parameter is required when authId is not populated.
Pattern: Max 40 alphanumeric characters
Example: "Fred Jones Bagels"

string

The currency code for amount. Use ISO 4217 numeric currency codes. This parameter is required when using this endpoint outside the United States.
Pattern: 3 digits
Example: "840"

number

The amount to be transferred from merchant to issuer in the settlement currency. Required when specialFunctions: make_multicurrency
Pattern: Positive integer or decimal number
Example: 100.00, 100, or 100.73

string

The currency code for settleAmount. Use ISO 4217 numeric currency codes. Required when specialFunctions: make_multicurrency.
Pattern: 3 digits
Example: "124"

number

The amount that will be posted to the cardholder account in the currency of the account. Required when specialFunctions: make_multicurrency.
Pattern: Positive integer or decimal number
Example: 100.00, 100, or 100.73

string

The currency code for cardBillingAmount. Use ISO 4217 numeric currency codes. Required when specialFunctions: make_multicurrency.
Pattern: 3 digits
Example: 484

string

The authorization ID (auth_id) as returned by the Create Simulated Card Authorization endpoint. If this parameter is not populated then merchantName is required.
Pattern: Positive integer
Example: 58344373

Headers
string
enum
Defaults to json

Use this header instead of the standard accept header to specify the response format.

Allowed:
Response

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

© Galileo Financial Technologies, LLC 2026    Privacy Disclosure

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of Galileo Financial Technologies, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of Galileo Financial Technologies, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.