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

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 the fet_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 a fet_id to set an account feature with the Set Account Feature endpoint.

This table does not include all fet_id values. If you retrieve a fet_id with Get Product Config that is not in this table, contact Galileo for the meaning.

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 the fet_id value.

📘

Note

This table does not include all fet_id values. If you retrieve a fet_id with Get Product Config that is not in this table, contact Galileo for the meaning.

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 of accountNo

📘

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.

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.

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.

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.

Parameters

Product parameters control the behavior and characteristics of individual products.

Where to see country blocks:

• GCC — Parameters page
• Get Product Config endpoint — Specify section: parameters

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 ATMs
• cnp_block — Card-not-present transactions, such as web and app purchases
• pos_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 of accountNo

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 or pct — 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 amount
• req_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 or pct — A flat fee or a percentage of the amount
• floor and ceiling — A minimum and maximum amount for the fee
• otype — The transaction type to apply the fee to
• fee_method — When there are insufficient funds for the fee, whether to pend the fee or drive the account negative
• exp_days — How many days before a fee expires from the pending queue
• excl_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 stock
• production_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 vendor
• stock_type — One of these codes:
  • CC (Card carrier)
  • CS (Card stock)
  • PM (PIN mailer)
  • WP (Welcome pack)

---