When setting up a Galileo's Secured Credit product, you must work with the sponsor bank and card network to create a business plan that meets bank and network requirements. This guide describes considerations for Galileo Secured Credit product.

## Obtaining bank and network approval

Before you can offer a secured credit product, you must get a sponsoring bank. The bank that holds your customer accounts may not sponsor secured credit. If this is the case, you will need to use a separate sponsor bank for secured credit.

When you set up a secured credit product, you are adding a new program with new BINs. You will need approval for the new BINs from both your sponsor bank and from the card network. From the card networks’ perspective, the card behaves more like a DDA than revolving credit, so it is important to be clear about why you want a credit BIN. You can ask your Galileo representative to help you with your conversation with the network to avoid misunderstandings.

## Underwriting and cardholder qualifications

Galileo does not provide underwriting. You must partner with a third-party underwriter to insure the accounts and to determine what qualifications a cardholder must have, such as minimum FICO score and minimum age.

## Fees and interest

If you decide to set up fees for your Galileo Secured Credit product, you determine what kinds of fees to assess, the fee amounts, and when and how to assess them. For secured credit products, Galileo supports either monthly or annual fee assessment with the <a href="ref:post_assessfee" target="_blank">Assess Fee</a> endpoint. Your Galileo representative can help you set up fee types for your program.

If you charge interest, you will need to calculate the amount and assess it from your own system. While there is a pending dispute on an account, you are responsible for stopping the accrual of interest and for adjusting the stoppage when the dispute is resolved.

## Billing cycles

Galileo offers three billing cycle configurations for secured credit products, which can be configured at either the program or product level, according to your business plan and the agreement with your sponsor bank. You can configure a billing cycle at the date of account creation, the week of account creation, or set one billing cycle for all accounts. Each secured credit billing cycle configuration is described in detail below.

For developer instructions on implementing billing cycles, see <a href="doc:developer-setup-for-galileo-secured-credit#implementing-billing-cycles" target="blank">Implementing billing cycles</a> under _Developer Setup for Galileo Secured Credit_.

### Billing cycle based on date of account creation

With this configuration, the customer’s billing cycle date is based on the date that the account is created. The billing cycle date can be any day within the range of 1–28. For example:

  • If an account is created on day 15, then the billing cycle date is the 15th.

  • If an account is created on day 29, 30, or 31, then the billing cycle date is the 28th.

This configuration is available only if Galileo handles your credit reporting and sends your reports to the credit bureaus.

### Billing cycle based on week of account creation

When you set this configuration, a customer is assigned a billing cycle date based on the week that the account is created. There are four possible billing cycle dates: 1, 8, 16, and 24. These dates are assigned as follows:

  • **Billing cycle day 1** — Assigned to accounts created between days 1–7.

  • **Billing cycle day 2** — Assigned to accounts created between days 8–15.

  • **Billing cycle day 3** — Assigned to accounts created between days 16–23.

  • **Billing cycle day 4** — Assigned to accounts created between days 24–31.

This configuration is available only if Galileo handles your credit reporting and sends your reports to the credit bureaus.

### One billing cycle for all accounts

With this configuration, you set a date within the range of 1–28 as the billing cycle date for all accounts. All customer billing cycles start on this date, regardless of when a customer account is created. This configuration may result in a shortened first billing cycle for some customers, depending on when the account was created.

This configuration is available for all credit reporting methods.

## Collateral account and money movement

For Galileo Secured Credit product, movement of funds into the collateral account is not automated by Galileo.

  • The account that funds are moved from must be an account capable of holding and transferring money, such as a Galileo-hosted <<glossary:DDA>>, savings account, or an external spending account. Other types of accounts are possible as well.

  • You determine when and how the cardholder can move funds into and out of the collateral account.

  • You can move funds into the collateral account with a <a href="ref:post_createaccounttransfer" target="_blank">Create Account Transfer</a> request.

  • You can move funds out of the collateral account with either a <a href="ref:post_createadjustment" target="_blank">Create Adjustment</a> or a <a href="ref:post_createpayment" target="_blank">Create Payment</a> request.

  • Your sponsor bank may have conditions for allowing customers to move funds out of the collateral account.

## Delinquency, default, and collections

For secured credit products that have a charge card, Galileo determines delinquency based on the first day of the customer's billing cycle and payment rules on the account. You determine when to send an account to collections. You may consider setting up a grace period before a delinquent account is defaulted. It is also common to set a spending block on delinquent accounts. Set up your internal system according to your business plan.

Note

Galileo can handle reporting only for secured credit products that operate as a charge card with the full amount due each period, and not other credit products like secured cards with revolving credit.

If you have Galileo prepare a Metro 2 credit report for you, Galileo will include each delinquent account in the report. For general information on credit reporting, see [Reporting to credit bureaus](🔗) in this guide.

You provide your own terms and conditions to state what happens when a cardholder does not pay back the credit line. Galileo does not automatically move funds from the secured credit account to pay back the amount owed. If necessary, you may have a debt facilitator assist with collections. Galileo does not recommend that you close the account when the cardholder defaults, but that you block spending instead.

## Reporting to credit bureaus

There is no legal requirement to report credit account activity to the three credit bureaus. Whether you report the charge card activity to the credit bureaus depends on whether you believe your cardholders will benefit from it. Reporting to the bureaus will most likely help your cardholders establish or improve their credit ratings because they are likely to have a low utilization rate relative to their credit limits. The boost a cardholder can expect in this case is around 35 points at first, and then gradual increases thereafter.

### Metro 2 reporting at Galileo

Note

Galileo can handle Metro 2 reporting only for secured credit products that operate as a charge card with the full amount due each period, and not other credit products like secured cards with revolving credit.

Galileo can prepare a Metro 2 credit report for you and then submit the report to the credit bureaus. This report is automatically generated once per month, the day after the customer’s billing cycle ends. To prepare the credit report, you will need to establish relationships with each of the credit bureaus to obtain a subscriber ID. This is a three-way contract between each of the three bureaus, you, and Galileo.

### Credit reporting and billing cycles

Your method of credit reporting may affect available options for [billing cycle configurations]().

If Galileo handles your credit reporting and sends your reports to the credit bureaus, you can choose any of the [three available billing cycle configurations](🔗) for your secured credit product. Galileo generates the report the day after the customer’s billing cycle date, regardless of the billing cycle configuration for your product.

If Galileo does not handle credit reporting for you, then your secured credit product will be configured with [one billing cycle for all accounts](🔗).

### Account closure status reporting

When a customer’s Galileo Secured Credit account closes, you can indicate the account closure status using Galileo’s Program API. If Galileo handles your credit reporting, Galileo will include the status in the Metro 2 report. A customer’s status at account closure may affect their credit score.

Note

Galileo can handle reporting only for secured credit products that operate as a charge card with the full amount due each period, and not other credit products like secured cards with revolving credit.

Account closure statuses indicate whether the amount owed was paid and who initiated the closure (the customer or the issuer). Account closure statuses are:

  • Account is unpaid, closed by the issuer, and charged off

  • Account is unpaid, closed by the issuer, and is in internal collections

  • Account takeover fraud, account closed by the issuer

  • Account is paid and closed by the issuer due to inactivity

  • Account is paid and closed at the customer’s request

For developer instructions to send account closure statuses see <a href="doc:developer-setup-for-galileo-secured-credit#reporting-account-closure-status" target="_blank">Reporting account closure status</a> under _Developer Setup for Galileo Secured Credit_.

### Delinquent account closures and reporting

You may set a policy to state that, when an account is delinquent, the account is closed, and the funds from the collateral account are used to pay the amount owed. If you do this, and Galileo generates your Metro 2 credit report for you, Galileo must report the account closure and delinquency to the credit bureaus.

If the account is closed after the report is sent, Galileo will not include the account in future reports. If the customer wants to reopen the account, you must create a new account instead and Galileo will report the new account to the credit bureaus. However, if you reopen the account before Galileo sends the report, Galileo will continue to include the account in future reports.

### Bankruptcy reporting

Galileo offers a feature for bankruptcy reporting to credit bureaus. Clients can request the _Bankruptcy Reporting_ guide for more information.

## Chargebacks and disputes

For charge cards associated with a secured credit product, you may be able to use the same chargeback process that you have for debit cards if the card network is the same. However, you are responsible for setting up your own internal process to handle disputes for fees and interest for the secured credit product. There is no provisional credit for a charge card.

## Statements and invoices

You can use RDFs and your own internal reporting to generate statements and invoices according to your agreement with your sponsoring bank. You can change the frequency of invoices depending on how far ahead you can float transactions. For example, you could have two billing cycles per month, or set up weekly billing cycles. See [Billing cycle](🔗) in this guide for more information.

## CST support for Galileo Secured Credit

This section describes features in the <<glossary:CST>> related to secured credit.

**Billing cycles**

CST fieldLocationDescription
Next Billing DateAccount Info > Account Details > Summary InformationThe customer’s next billing cycle start date.

## Galileo setup

ParameterLevelDescription
ALWNBProductControls whether a call to the <a href="ref:post_createadjustment" target="_blank">Create Adjustment</a> endpoint can drive an account balance negative. When this parameter is set to `1`, a call to the Create Adjustment endpoint can drive the balance negative.
BCDAYProductControls the length of time to wait after the bill cycle start date before setting the bill cycle and assessing fees. Use an integer to specify the number of days or `MONTH` to indicate a one month bill cycle.
CYCLEProductControls whether to assess maintenance fees monthly (`MON`) or yearly (`YER`). Weekly assessment is not available for secured credit products. Works in conjunction with CYMET.
CYDAYProductSpecifies the day of the month to assess fees when CYCLE is set to `MON`. Valid values are `1–28`. Weekly assessment is not available for secured credit products.
CYMETProductControls whether to assess a fee by account (PRN) or balance (`bal_id`). This parameter also controls what happens if the balance is lower than the fee amount. Values for secured credit products are:<li> `A` — Set an independent bill cycle for each account and assess fees by account.<li> `B` — Set the same bill cycle for all accounts on the same balance and assess fees by balance.<li> `HAD` — Hybrid account. Assess fees by account and defer the fee if it will drive the balance negative.<li> `HAP` — Hybrid account. Assess fees by account and charge a partial fee if the entire fee will drive the balance negative. This effectively takes the balance to 0.<li> `HBD` — Hybrid account. Assess fees by balance and defer the fee if it will drive the balance negative.<li> `HBP` — Hybrid account. Assess fees by balance and charge a partial fee if the entire fee will drive the balance negative.
BRCDTProgram or ProductControls the customer billing cycle date. Values for secured credit products are:<li> Integer (1–28) — Specifies the customer billing cycle date for all accounts in the program. Yields one billing cycle date for all accounts. <li> `ACCOUNT_DATE` — Sets the billing cycle date to the day that the account is created. If an account is created on day 29, 30, or 31, then the billing cycle date is 28. Yields 28 possible billing cycle dates. <li>`1, 8, 16, 24` — Sets the billing cycle date based on the week that the account is created. Possible dates are 1, 8, 16, and 24. Yields four possible billing cycle dates.