Create Simulated Card Settlement

post

https://api-{corename}.{env}.gpsrv.com/intserv/4.0/createSimulatedCardSettle

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
Do not use this endpoint in Production.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Form Data

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 PRN or 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), star (STAR), mc_auth (Mastercard), coop (Co-op), or visa_baseii (Visa Base II).
Pattern: visa, mc_auth, visa_baseii, star, coopExample:"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 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 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 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 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

Headers

response-content-type

string

enum

Defaults to json

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

Allowed:

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Response

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/xml

default