--- title: "Create Simulated Card Settlement" method: POST path: "/createSimulatedCardSettle" tags: ["Transaction Simulation"] --- # Create Simulated Card Settlement `POST /createSimulatedCardSettle` ## Request - Base URL: `api-{corename}.{env}.gpsrv.com/intserv/4.0/` (relative, and the document’s source URL is not known) - URL: `api-{corename}.{env}.gpsrv.com/intserv/4.0/createSimulatedCardSettle` - Auth: none declared Use the Create Simulated Card Settlement endpoint to settle a simulated card authorization in the <> 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. [block:callout] { "type": "warning", "title": "Warning", "body": "This endpoint does not support XML responses. If you pass `response-content-type: xml`, it will be ignored." } [/block] [block:callout] { "type": "warning", "title": "Warning", "body": "Do not use this endpoint in <>." } [/block] ## Request body `application/x-www-form-urlencoded` - object - `apiLogin` string, required: Web service username, as provided by Galileo. Pattern: Max 50 characters Example: `"AbC123-9999"` - `apiTransKey` string, required: Web service password, as provided by Galileo. Pattern: Max 15 characters Example: `"4sb62fh6w4h7w34g"` - `providerId` integer, required: Galileo-issued provider identifier. Pattern: Max 10 digits Example: `9999` - `transactionId` 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"` - `accountNo` string, required: The <> or <> of the account. Pattern: PAN or PRN Example: `"074103447228"` - `amount` 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` - `association` string, required: Specifies which card network to simulate: `visa` (Visa), `mc_auth` (Mastercard Credit). Pattern: string Example: `"visa"` - `merchantName` 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"` - `currencyCode` 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"` - `settleAmount` number: The amount to be transferred from merchant to issuer in the settlement currency. Required when `currencyCode` differs from the account currency, or when `specialFunctions: make_multicurrency`. Pattern: Positive integer or decimal number Example: `100.00`, `100`, or `100.73` - `settleCurrencyCode` string: The currency code for `settleAmount`. Use ISO 4217 numeric currency codes. Required when `currencyCode` differs from the account currency, or when `specialFunctions: make_multicurrency`. Pattern: 3 digits Example: `"124"` - `cardBillingAmount` number: The amount that will be posted to the cardholder account in the currency of the account. Required when `currencyCode` differs from the account currency, or when `specialFunctions: make_multicurrency`. Pattern: Positive integer or decimal number Example: `100.00`, `100`, or `100.73` - `cardBillingCurrencyCode` string: The currency code for `cardBillingAmount`. Use ISO 4217 numeric currency codes. Required when `currencyCode` differs from the account currency, or when `specialFunctions: make_multicurrency`. Pattern: 3 digits Example: `484` - `authId` 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` ## Response `default` - object - `status_code` integer, nullable, required: The response status code. May return a string for some statuses. - `status` string, nullable, required: The condition of a process or response - `processing_time` number, nullable, required: The time elapsed in processing the transaction - `echo` object, nullable, required: A structure that contains transaction ID information - `transaction_id` string, nullable, required: An ID that represents an API transaction - `provider_timestamp` string, date-time, nullable, required: Store a related timestamp for reporting and troubleshooting purposes - `provider_transaction_id` string, nullable, required: Secondary transaction identifier (generated by a provider) - `system_timestamp` string, date-time, nullable, required: A system generated timestamp - `rtoken` string, nullable, required: A Galileo-generated ID used for tracking - `errors` string[]: A list of errors generated while the request was processed - `response_data` object, nullable, required: A structure for the response data. It can be empty but usually will contain information. - `settle_response_code` string, required: A code used to give the status of the simulated auth settlement - `settle_response_description` string, required: A description of the settlement response - `settle_dtl` string, required: An ID associated with the simulated settlement ## Changes - **2026-11-03** `1ede7567a879`: 1 info - endpoint added [Operation history](https://skmtc.dev/galileo-ft/apis/program-api/changes/createSimulatedCardSettle/post.md) --- [API](https://skmtc.dev/galileo-ft/apis/program-api.md) - [All operations](https://skmtc.dev/galileo-ft/apis/program-api/llms.txt) - [OpenAPI document](https://skmtc.dev/galileo-ft/apis/program-api/revisions/1ede7567a879?raw)