This section contains workflows that illustrate the processes for creating and managing secured credit products.
This flowchart is an example of how you might structure a product with a secured credit account. Your Galileo representative can help you build a process that works in your own system. Steps are described below.
- A new customer requests a secured credit account.
- You send the Create Account endpoint to create the DDADDA - Demand deposit account. The banking-industry term for an account from which funds can be withdrawn at any time, such as a checking account..
- You send the Add Account endpoint to create the charge card account and link it to the DDA.
- You send the Add Account endpoint a second time to create the secured credit account and link it to the DDA.
- Galileo sends you the
CAPP: app_completedevent for the DDA .
- The account holder deposits funds into the secured credit account. This establishes the account credit line.
- Galileo sends the charge card to be embossed.
- The customer receives the charge card and requests to activate it.
- You send the Activate Card endpoint to activate the charge card.
- For a credit card with variance granted, you follow the appropriate PIN-set procedure (see the PIN Set Procedures guide).
With a secured credit product, a card transaction is settled against the secured credit account, as shown in this flowchart. Steps are described below.
- An account holder makes a purchase over card network rails and the card network sends an authorization request.
- You or Galileo approve the authorization request based on the available balance in the account holder's secured account, which matches the credit line.
- If the authorization request is approved, Galileo places a hold for the authorized amount, which reduces the account holder’s available balance on the secured account. Galileo sends the
BAUT: authevent with the available balance in the
- The card network sends the settlement batch file.
- Galileo directs the issuing bank to pay the card network.
- Galileo backs out the authorization hold and sends you the
- The monthly invoice is sent to the account holder and the issuing bank receives repayment.
- If the account holder cannot pay down the credit line from the DDA, funds are recovered from the secured credit account. See the Secured credit default and delinquency workflow.
See About Card Transactions for more information on authorization and settlement over card network rails.
This flowchart illustrates funds flow between the DDADDA - Demand deposit account. The banking-industry term for an account from which funds can be withdrawn at any time, such as a checking account. and secured credit account. Steps are described below.
- The account holder requests to move funds between the DDA and the secured credit account.
- You send the Create Account Transfer request.
- Funds are transferred and the secured account balance increases or decreases.
- You send Set Credit Limit to update the credit line based on the funds in the secured account.
This flowchart illustrates the process that occurs when an account with a secured credit line goes into default or is delinquent. Steps are described below.
- An account with a secured credit line goes into default or repayment is delinquent.
- You calculate the default or delinquency and send Set Account Feature twice, to report the amount and date to Galileo.
- Galileo prepares a report to be sent to the credit bureaus. You can review and add details to the report before it is sent.
- You send Set Credit Limit to update the credit limit.
- You send Modify Account or Card Status to update the account status.
- The collateral funds in the secured credit account are used to repay the credit line.
Updated 27 days ago