---
title: "Create Simulated Card Authorization"
method: POST
path: "/createSimulatedCardAuth"
tags: ["Transaction Simulation"]
---

# Create Simulated Card Authorization

`POST /createSimulatedCardAuth`

## 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/createSimulatedCardAuth`
- Auth: none declared

Use the Create Simulated Card Authorization endpoint to simulate a card authorization in the <<glossary:CV>> environment. This endpoint creates but does not settle a card authorization for the account and returns a response code and its description with the `auth_id`. 
- Capture the `auth_id` to settle the transaction with <a href="ref:post_createsimulatedcardsettle" target="_blank">Create Simulated Card Settlement</a>.
- For instructions on using this endpoint see <a href="doc:simulating-card-transactions" target="_blank">Simulating Card Transactions</a>.

[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 <<glossary:Production>>."
}
[/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 <<glossary:PRN>> or <<glossary:PAN>> 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).<!--`mc_debit` (Mastercard Debit), `star` (STAR), `coop` (Co-op), `visa_baseii` (Visa Base II), or `allpoint` (Allpoint).--> 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"`
  - `acquirerId` string: Simulated acquirer ID. If this value is not passed, the simulator inserts a random 6-digit number. Pattern: 6-digit number Example: `437723`
  - `terminalId` string: Simulated terminal ID. If this value is not passed, the simulator inserts a random 8-digit number. Pattern: 8-digit number Example: `57395783`
  - `merchantId` string: Simulated merchant ID. If this value is not passed, the simulator inserts a random 15-character alphanumeric string. Pattern: Max 15 alphanumeric characters Example: `"asdf45sdf6sd3d0a"`
  - `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`
  - `mcc` string: ISO 18245 merchant category code. Pattern: 4 digits Example: `3408`
  - `originalAuthId` string: The `auth_id` of the previous authorization in a series, such as with a completion, reversal or incremental authorization. Required when `transType` is `3`, `4`, `5` or `6` (Visa) or `3` (Mastercard) or `4`, `5`, `6` (Star). Pattern: Numerals Example: `30582`
  - `specialFunctions` string: Additional function to add to the simulated transaction. See the <a href="ref:api-reference-special-functions" target="_blank">Special Functions</a> enumeration for valid values. Pattern: Max 100 characters Example `"add_cashback"`
  - `posEntryMode` string: The first two characters of DE022. Specifies how the PAN was entered, such as magnetic stripe, EMV chip or contactless. See <a href="ref:api-reference-de022-codes" target="_blank">DE022 Codes</a> for possible values. Valid only when `association: visa`. Pattern: 2 characters Example: `01`
  - `requesterId` string: An identifier for the entity that makes a tokenization request. Required when `specialFunctions: make_tokenized`. Pattern: Numerals Example: `3030303`
  - `walletId` string: Identifier for the mobile wallet that contains the card that was used for the transaction. Required when `association: mc_auth` and `specialFunctions: make_tokenized`. Pattern: Numerals Example: `474747474`
  - `latitudeAndLongitude` string: The latitude and longitude of the point of sale. Valid only when `association: visa` and `transType: 17`. Default: `40.76078/-111.89105` (Salt Lake City, UT) Pattern: 99.99999/-99.99999 Example: `"40.76078/-111.89105"`
  - `partialAmount` number: Amount of a partial authorization. Valid only when `association: mc_auth` and `specialFunctions: make_partial_reversal`. Pattern: Integer or decimal amount Example: `100.00`, `100`, or `100.73`
  - `partialForeignAmount` number: Amount of a partial authorization when the point of sale is a different country than the account. Valid only when `association: mc_auth` and `specialFunctions: make_partial_reversal`. Pattern: Integer or decimal amount Example: `100.00`, `100`, or `100.73`
  - `cashbackAmount` number: Amount in `localAmt` that is provided in cash. Valid only when `association: mc_auth` and `specialFunctions: make_cashback`. Debit accounts only. Pattern: Integer or decimal amount Example: `100.00`, `100`, or `100.73`
  - `cashAdvanceAmount` number: Amount in `localAmt` that is provided in cash. Valid only when `association: mc_auth` and `specialFunctions: make_cashback`. Credit accounts only. Pattern: Positive integer or decimal number Example: `100.00`, `100`, or `100.73`
  - `pin` string: To include the PIN that is already set for the card, leave this value blank and pass `specialFunctions: add_pin` (Visa) or `specialFunctions: make_debit` (Mastercard). Pass a value for this parameter to use that value in the request and also to change the PIN for the card. Pattern: 4 digits Example: `4395`
  - `transType` integer: The type of transaction to simulate. See the <a href="ref:api-reference-simulated-transaction-types" target="_blank">Simulated Transaction Types</a> enumeration for valid values. Pattern: 1 or 2 digits Example: `3`

## 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.
    - `auth_response_code` string, required: A code used to give the status of the simulated auth
    - `auth_response_description` string, required: A description of the authorization response
    - `auth_id` string, required: An ID associated with the simulated auth

## Changes

- **2026-11-03** `1ede7567a879`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/galileo-ft/apis/program-api/changes/createSimulatedCardAuth/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)