Product Settings
Consult this page to see some of the settings that are available for Galileo products. Galileo collects these settings in a Product Setup Guide to pass to the operations team for product setup.
Use this page for these purposes:
- When evaluating Galileo capabilities, to see Galileo product properties
- When planning how to set up your products, to see which options to choose
- When using the Get Product Config endpoint, to interpret the values
- When viewing your product settings in the Galileo Client Console (GCC)
Table of contents
- Product info
- Account features
- Card features
- Auth limits
- Load limits
- Transfer limits
- Parameters
- Country blocks
- MCC blocks
- Upcharges
- Fees
- Emboss partners
- Emboss stock
Product info
Your general product information includes these items. You can view them in these places:
- GCC — Product Info page
- Get Product Config endpoint — Specify
section: info
Setting | Description | Get Product Config response field |
---|---|---|
Product ID | A Galileo-generated identifier for your product, unique across the Galileo platform | product_id |
Program ID | A Galileo-generated identifier for the product's program, unique across the Galileo platform | program_id |
Product name | A descriptor for your product, such as "Personalized Visa" or "Overdraft Account" | name |
Product category | See the Product Categories enumeration for valid values | product_category |
Product type | See the Product Types enumeration for valid values | product_type |
Segment | Which segment this product is intended for: business or consumer | is_business_product |
Core | The name of your core (database), where your data resides | db |
Base BIN | Card product only. The BIN that your bank assigned to you. See PAN Logic for more information. You can have more than one BIN for your product. | base_bin |
Card expiry | Card product only. The number of years before a card expires | yrs_card_is_valid |
Auth expiry | Card product only. Default number of days before an authorization expires, unless it is settled or completed | auth_days_to_expire |
Gas upcharge | Card product only. The upcharge amount at gas pumps | gas_auth_amt |
Max PIN retries | Card product only. The maximum number of failed PIN tries before the PIN is locked | max_pin_retries |
Card Art ID | Card product only. Default designator for the card art for this card. You can have more than one card-art image for your product. | issuer_card_art_id |
Service code | Card product only. Authentication method(s) of the physical card: magstripe, EMV, and/or contactless | svc_code |
ACH hold days | ACH support only. The number of business days to hold outgoing ACH debits before depositing funds into the account | hold_days |
Minimum activation balance | Minimum account amount before the account can be activated | min_act_amt |
Customized auth expiries
You can set authorization expiration intervals per MCC in addition to the standard expiry. For example, you can determine that hotel authorizations expire after 30 days and car rentals expire after 15 days.
You can view custom authorization expiries in these places:
- GCC — MCC Expirations page
- Get Product Config endpoint — Specify
section: mcc_expirations
.
For each auth expiry, you can configure these settings:
- MCC or MCC group (hotel, airline, car rental)
- Whether to match the MCC only, to also match the amount, or to match the product ID
- The authorization type to apply to the expiry
Account features
This table displays most of the common account features to set. You can set multiple account features for your account. In some cases, Galileo will set the account feature automatically, upon account creation, and in other cases you must use the Set Account Feature endpoint to set the feature on individual accounts.
You can view account features in these places:
- GCC — Default Account Settings page
- Get Product Config endpoint — Specify
section: account_features
. Returns thefet_id
value. - Get Account Features endpoint — Returns the
feature_type
value for those features that you can set or update with Set Account Feature.
Note
The
fet_id
is an internal value only. Do not attempt to use afet_id
to set an account feature with the Set Account Feature endpoint.This table does not include all
fet_id
values. If you retrieve afet_id
with Get Product Config that is not in this table, contact Galileo for the meaning.
fet_id | featureType | Description | Value type |
---|---|---|---|
9 | Enable Western Union SwiftPay | 0 or 1 | |
10 | 8 | Permit international (foreign) transactions | Y or N |
11 | 6 | Permit card-not-present transactions | Y or N |
12 | 2 | Opt in to paper statements | Y or N |
13 | 13 | Enable Metro2 credit reporting | Y or N |
14 | 1 | Billpay reporting enabled | Y or N |
15 | PRN of overdraft account | 12-digit number | |
16 | 17 | Overdraft account eligibility:E — eligibleP — participatingI — ineligible | E or P or I |
18 | Maximum secured balance. For secured credit products, not revolving-credit products. | Decimal amount | |
26 | Savings account for a GPR account. PRN of the savings account associated with a GPR. | Integer | |
28 | Original prod_id of the overdraft account | Integer | |
31 | 7 | Enable ACH early access | Y or N |
34 | 25 | Second line emboss text. Second line under cardholder name | string |
36 | Low-balance message-sent flag | 0 or 1 | |
37 | Original prod_id after product switch | prod_id | |
38 | Sent velocity-limit alert flag | Y or N | |
39 | 16 | Card image ID and status: image ID (9 char) pipe (|) status (1 char) | String |
44 | Override certain fraud rules based on cardholder response to SMS message, comma-separated list of rule names to not run | String | |
45 | 14 | Override fraud rules engine checking. If Y , the auth process doesn't check fraud rules. | Y or N |
46 | Product-switch counter, number of times the product has been switched | Integer | |
47 | 9 | Disable ATM withdrawals for the cardholder (cash advance still allowed) | Y or N |
48 | 10 | Disable cash advances for the cardholder (ATM still allowed) | Y or N |
49 | 11 | Enable roundup on account | Y or N |
64 | Deposit sweeps account created. Y means a deposit-sweeps account has been created for this account. | Y or N | |
65 | 20 | Token transactions only. If set to Y , only transactions with a token are permitted for this account. When this value is Y , fet_id: 66 cannot be set to Y . | Y or N |
66 | 21 | Card-present token transactions only. If set to Y , a token is required for card-present transactions. When this value is Y , fet_id: 65 cannot be set to Y . | Y or N |
67 | 22 | Block token transactions. If set to Y , only transactions without a token (non-mobile wallet) are permitted for this account. | Y or N |
69 | Savings account tier for SAVMI. The prod_id of a savings account that is linked to this primary account, If both this and SAVPI are defined, this is given priority. | Integer | |
71 | 23 | First delinquent date for Metro2 credit report | String "MMDDYYYY" |
72 | 24 | Delinquent amount for Metro2 credit report | Decimal number |
75 | Selective DFE or PRP rule suppression. You can turn on selective fraud rule suppression in the CST, or using Set Account Feature, which will suppress only the fraud rules that you choose and leave the safety-net fraud rules firing. | Y or N | |
76 | Account closure reason. Contains the reason why a client is closing an account. This value translates to the account status and special comment that is reported to credit bureaus when the account is reported as closed. Possible values:chargeoff — Unpaid, closed by issuer, and charged offcollection — Unpaid and closed by issuerdeleted_fraud — Account takeover fraud, closed by issuerinactivity — Paid and closed by issuer due to inactivitypaid_user — Paid and closed at the customer's request | String | |
79 | 30 | Delay emboss. If set to Y , the emboss process skips the card-creation process. | Y or N |
80 | Skip expedited mail fee. If set to Y , the emboss process waives the expedited mail fee. | Y or N |
Card features
Card features apply to individual cards, not to the accounts. Card features are set by back-end processes unless otherwise noted.
You can view card features in these places:
- GCC — Default Card Settings page
- Get Product Config endpoint — Specify
section: card_features
. Returns thefet_id
value.
Note
This table does not include all
fet_id
values. If you retrieve afet_id
with Get Product Config that is not in this table, contact Galileo for the meaning.
fet_id | Description | Value type |
---|---|---|
10 | Freeze card. Set by internal processes, the CST, or by the Modify Status endpoint type: 17 or 18 | Y or N |
11 | Offline PIN-block to be pushed via script | Y or N |
12 | Whether the offline PIN-block has been pushed | Y or N |
13 | High-risk card | Y or N |
19 | Application transaction counter (ATC) for contactless authentication | Integer |
21 | Ingo card ID | String |
22 | Digital First. Emboss the card regardless of card status (FEMBO is set to Y ) | Y or N |
23 | pin_access_token for the PIN Retrieval Service | String |
24 | Transaction info for single-use virtual cards. JSON string with terminal_id , merchant_id , and transaction_amount | String |
Auth limits
Authorization limits control the amount and transaction count of various types of authorization and preauthorization requests. These limits are sometimes called "velocity controls."
Where to see auth limits:
- GCC — Authorization Limits page
- Get Product Config endpoint — Specify
section: auth_limits
- Get Auth Control endpoint — Populate
prodId
instead ofaccountNo
Note
Authorization limits can also be set on a per-account basis. See Account-Level Authorization Controls for more information.
For every authorization limit, you can configure these settings. An asterisk (*) means that it is required.
Setting | Description | Valid values | Get Product Config response field | Get Auth Control response field |
---|---|---|---|---|
Limit category* | Name or descriptor of the limit, either preset or custom | String | limit_cat | control_desc |
Period* | The timespan for the limit. The format is [numeral][D|T|M] , where:D – Calendar day, from 00:00:00 to 23:59:59 in Galileo system timeT — Single transactionM — Calendar month; a rolling 30-day period is 30D | 1D , 1T , 30D , 1M , 7D , etc. | period | period |
Amount | Amount of the limit. Required only if there is no count. Both amount and count can be set at the same time. | Decimal amount | amt | amount |
Count | Transaction count for the limit. Required only if there is no amount. Both amount and count can be set at the same time. | Integer | cnt | transaction_count |
Transaction type* | Type of transaction affected by the limit. Minimum of one, but multiple can be selected. | ATM — Automated teller machineCAD — Cash advance (over-the-counter, teller)CBA — Cash back (at point of sale)POS — Point of saleVFT — Visa funds transfer | n/a | trans_type |
Domestic flag | Whether domestic or international transactions are affected. Default: both | Y — Domestic onlyN — International onlyA — Both domestic and international | domestic_flag | domestic_flag |
PIN flag | Whether PIN or signature transactions are affected. Default: both | Y — PIN onlyN — Signature onlyA — Both PIN and signature | has_pin_flag | has_pin |
Contactless flag | Whether contactless or non-contactless transactions are affected. Default: both | Y — Contactless onlyN — Non-contactless onlyA — Both contactless and non-contactless | contactless_flag | n/a |
Velocity or control ID | Galileo-generated ID for the limit, used when setting account-level controls. | Integer | velocity_id | control_id |
Auth limit presets
These limits are preconfigured in the Galileo system. Some of them are required. In a typical setup, ATL, CAL, TAT, TCA, and TOL have the same limit amount.
limit_cat | Description | period | Required |
---|---|---|---|
ATL Daily Limit | Daily ATM withdrawal limit | 1D | X |
ATM CNT Withdrawals | Daily ATM withdrawal count. Default: 200 | 1D | X |
CAL Daily Limit | Daily over-the-counter limit | 1D | X |
PCL Daily Limit | Total daily limit (POS, cash advance, ATM withdrawal, etc.) This is usually a combination of POL and standard withdrawal for ATL, CAL, TAT, TCA, and TOL. For example, if POL is $1,000, and standard withdrawal is $500, then TOL is usually $1,500. | 1D | X |
POL Daily Limit | Daily point-of-sale limit | 1D | X |
TAT Per Transaction Limit | Per-transaction ATM withdrawal limit | 1T | |
TCA Per Transaction Limit | Per-transaction over-the-counter limit | 1T | |
TOL Daily Limit | Total daily cash withdrawal limit | 1D | X |
Customized auth limits
You have the option to create customized auth limits in addition to the preset limits. Each customized limit must have these settings at minimum:
- Limit category (description)
- Amount or count or both
- At least one transaction type
- Period
As desired, you can also set the flags for domestic, PIN, and contactless transactions.
Load limits
With load limits you control funds that are deposited into accounts.
Where to see load limits:
- GCC — Load Limits page
- Get Product Config endpoint — Specify
section: load_limits
For each load limit you can configure these settings. Consult Load-Limit Types for all limit_type
values.
Setting | Description | Valid values | Get Product Config response fields |
---|---|---|---|
Load otype | The otype of the load | Load Types | load_type |
Maximum card balance | The maximum balance allowed on the card account at any one time. | Decimal | limit_type: 5 , value |
Maximum per transaction | Maximum amount per load transaction | Decimal | limit_type: 1 , value |
Minimum per transaction | Minimum amount per load transaction | Decimal | limit_type: 2 , value |
Maximum daily amount | Maximum amount per day | Decimal | limit_type: 3 , period: 1 , value |
Maximum daily count | Minimum count per day | Integer | limit_type: 4 , period: 1 , value |
Maximum monthly amount | Maximum amount per month | Decimal | limit_type: 3 , period: 30 , value |
Maximum monthly count | Minimum count per month | Integer | limit_type: 4 , period: 30 , value |
Maximum lifetime amount | Maximum amount over the lifetime of the account | Decimal | limit_type: 8 , value |
Maximum lifetime count | Minimum count over the lifetime of the account | Integer | limit_type: 9 , value |
Reject mode | What to do with a load request when a limit would be exceeded | Y — Reject the load N — Pend the load until it can be posted | reject |
Delayed posting | Interval to delay the posting of a load. | Number of minutes, hours, or days | limit_type: 10 , value |
Transfer limits
Transfer limits (send limits) control funds that are adjusted out of accounts.
Where to see transfer limits:
- GCC — Outgoing Transaction Limits page
- Get Product Config endpoint — Specify
section: trans_limits
For each transfer limit you can configure these settings. Consult Transfer-Limit Types for all limit_type
values.
Setting | Description | Valid values | Get Product Config response fields |
---|---|---|---|
Transfer otype | The otype of the transfer | Transfer Types | trans_type |
Maximum per transaction | Maximum amount per adjustment | Decimal | limit_type: 101 , value |
Minimum per transaction | Minimum amount per adjustment | Decimal | limit_type: 102 , value |
Maximum periodic amount | Maximum amount per period | Decimal | limit_type: 103 , period , value |
Maximum periodic count | Minimum count per period | Integer | limit_type: 104 , period , value |
Maximum available balance | Maximum balance for a debit account | Decimal | limit_type: 105 , value |
Minimum available balance | Minimum balance for a debit account | Decimal | limit_type: 106 , value |
Maximum available credit | Maximum amount of available credit | Decimal | limit_type: 109 , value |
Minimum available credit | Minimum amount of available credit | Decimal | limit_type: 110 , value |
Minimum first-transaction amount | Minimum amount for the account's first transaction | Decimal | limit_type: 112 , value |
Parameters
Product parameters control the behavior and characteristics of individual products.
Where to see parameters:
- GCC — Parameters page
- Get Product Config endpoint — Specify
section: parameters
These are the fields in the parameters
list.
param_id
— The name of the parameter, typically 5 charactersvalue
— The value that has been set for the parameter.
Product parameters are listed on the Parameters page.
Country blocks
You can decide to block card transactions by ISO 3166-1 numeric country code.
Where to see country blocks:
- GCC — Country Authorization Rules page
- Get Product Config endpoint — Specify
section: country_block
These are the transaction types you can block:
cash_block
— Cash withdrawals from ATMscnp_block
— Card-not-present transactions, such as web and app purchasespos_block
— Point-of-sale transactions, in-person transactions at retail locations
As desired, you can also block cash withdrawals during certain times of day, such as blocks during the night hours.
MCC blocks
You can block card transactions per MCC. You can also block transactions per MCC on an individual account level. See MCC Control Design for more information.
Where to see MCC blocks:
- GCC — MCC Blocks page
- Get Product Config endpoint — Specify
section: mcc_blocks
- Get MCC Controls endpoint — Populate
prodId
instead ofaccountNo
Each MCC control has these characteristics:
- Beginning and end MCC in the range
- Whether the range is denied or allowed
- Whether the control is applied only to online transactions
Upcharges
To help avoid settlements that drive the account negative, you can assign upcharges per MCC.
Where to see upcharges:
- GCC — MCC Upcharges page
- Get Product Config endpoint — Specify
section: mcc_upcharges
For each upcharge you can configure these settings:
amt
orpct
— A flat amount or a percentage of the total sale- MCC range — The MCCs to include
replace_flag
— Whether to replace (Y
) the authorization amount with the upcharge or add the upcharge to the amountreq_amt_limit
— Set a threshold to apply the upcharge to amounts equal to or lower than this amount
Fees
Galileo has configured a wide assortment of fee types that you can select. To see the fees that have been assessed on a particular account, use the Get Fee History endpoint.
Where to see product fees:
- GCC — Fees page
- Get Product Config endpoint — Specify
section: fees
For each fee you can set these values:
amt
orpct
— A flat fee or a percentage of the amountfloor
andceiling
— A minimum and maximum amount for the feeotype
— The transaction type to apply the fee tofee_method
— When there are insufficient funds for the fee, whether to pend the fee or drive the account negativeexp_days
— How many days before a fee expires from the pending queueexcl_fees_status
— Account statuses for which a fee is not assessed
Emboss partners
If you offer a physical card, you must set up a relationship with an emboss vendor. Galileo is integrated with many emboss vendors that you can choose from.
Where to see emboss partners:
- GCC — Emboss Details page
- Get Product Config endpoint — Specify
section: emboss_partners
The Get Product Config endpoint returns the file mask to use for the vendor.
Emboss stock
Also for physical cards, you must decide on the materials for your card, such as plastic, metal, or wood.
Where to see emboss stock:
- GCC — Emboss Details page
- Get Product Config endpoint — Specify
section: emboss_stock
The Get Product Config endpoint returns these values:
dscr
— Description of the card stockproduction_type
— One of these codes:01
(New issuance)02
(Replacement issuance)03
(PIN mailer only)04
(Welcome pack only)
stock_no
— Assigned by your emboss vendorstock_type
— One of these codes:CC
(Card carrier)CS
(Card stock)PM
(PIN mailer)WP
(Welcome pack)