This guide is intended to provide a general outline of new Galileo functionality prior to its release to production. The information in this guide is therefore subject to change as development proceeds and is not a guarantee of future functionality. If you are interested in this feature, contact Galileo for details.
This guide explains how to test Corporate Credit Limits (CCL) in the CV environment using the Program API. Do not follow this procedure to test in Production.
Along with this guide you might want to read these:
- Corporate Credit Limits — Explanation of what Corporate Credit Limits are, with use cases.
- Creating Corporate Credit Accounts — Properties of CCL accounts and how to set them up.
- Corporate Credit Limit Transaction Examples — How various Corporate Credit Limit transaction types look in the ledger.
In this scenario you will:
- Create a CCL funding account
- Set a credit limit
- Create one or more CCL spending accounts
- Simulate a card authorization and settlement
- View the authorization/settlement as well as the funding transactions
- Adjust the available credit
Remember that the CV environment runs on Galileo system time.
Work with Galileo to set up your CCL funding and CCL spending products in CV. Galileo recommends that you configure all of the settings that you intend to use in Production.
At minimum, the funding product should have these characteristics:
- Product otype 0
- Product category 32
At minimum, the spending product should have this characteristic:
- Product category 33
Follow these steps to create a CCL funding and a CCL spending account.
- Call Create Account with these parameters:
|CCL funding product ID|
|Required if |
- In the response, capture the
pmt_ref_no(PRN) for future use.
- Check the status of the CCL funding account by calling Verify Account with this parameter:
accountNo:PRN of the CCL funding account
- If the
N, activate the CCL funding account by calling Modify Status with these parameters:
To set the credit limit on the CCL funding account, call Set Corporate Credit Limit with these parameters:
- Call Create Account with these parameters.
|CCL spending product ID|
|Required if |
- Capture the these values from the response:
- Last four digits of
- As desired, create a second CCL spending account, such as a card with a different CCL spending account product ID.
After creating the CCL spending card, call Activate Card with these parameters:
|PRN or CAD of the CCL spending account|
|Optional. Last four digits of card_number. If there is more than one card associated with the PRN, you must populate this parameter.|
- To verify that the card has been activated, call Get Card with the PRN or CAD of the card for
accountNo. Inside the
embossed_cardsobject you should see
To see the relationship between the CCL funding and CCL spending accounts, call Get RTF Account Relationship with this parameter:
accountNo:PRN of the CCL funding account, which returns all of the spending accounts that are associated with it.
Alternatively, you can call the endpoint with a CCL spending account PRN for
accountNo to return the associated CCL funding account.
- To simulate a simple card transaction in CV, call the Create Simulated Card Authorization endpoint with these parameters:
|PAN or CAD of the CCL spending card|
|Populate this parameter only when the currency of the program is not |
- Capture the
auth_idfor future use.
- Settle the transaction by calling the Create Simulated Card Settlement endpoint with these parameters:
|PAN or CAD of the CCL spending card|
To see the transactions that were created, call Get All Transaction History twice:
accountNo— PRN of the CCL funding account
accountNo— PRN of the CCL spending account
For the CCL spending account you should see four transactions. The
source_id are example values only.
For the CCL funding account, you should see one transaction.
For the funding account, call Get Corporate Credit Summary. This should be the result:
The cards can continue spending until the
available_credit reaches 0. After that, all authorization requests are denied until one of these events happens:
- The credit limit is increased.
- Funds are added to the funding account, such as to pay some or all of the balance.
For the CCL funding account, call Get Balance. This should be the result:
That is the amount owed on the CCL funding account. To pay it off, you can apply the funds to either the CCL spending account or the CCL funding account. If you apply funds to the spending account, they will be transferred into the funding account.
For this example, call Create Adjustment for the CCL spending account with these parameters:
|Any unique 64-bit integer. In Postman you can use the |
|PAN or PRN of the CCL spending account|
Alternatively, you can use Create Payment to apply the funds, using the same
You do not need to add funds to the funding account for the spending cards to have available funds—setting a credit limit is enough. However, you can add funds in excess of the balance owed, which increases the available amount to spend.
Call Create Adjustment for the CCL funding account with these parameters:
|Any unique 64-bit integer.|
|PRN of the CCL funding account|
Call Get Corporate Credit Summary for the funding account. This should be the result:
The available credit is higher than the credit limit by 500.00. The spending cards now have a 1500.00 spending limit, without needing to change the credit limit.
Alternatively, you can call Set Corporate Credit Limit to set the credit limit to 1500.00.
To simulate a Visa transaction instead of the Mastercard transaction shown above, pass
association: visa. In the response to Get All Transaction History, the transaction codes will be:
- VIA — Authorization
- BVA — Backout
- VSA — Settlement
For other types of transactions, see the Simulating Card Transactions guide.
Updated 2 months ago