Testing Corporate Credit

This guide explains how to test Corporate Credit (CC) transactions 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:

In this scenario you will:

  1. Create a CC funding account
  2. Set a credit limit
  3. Create one or more CC spending accounts
  4. Simulate a card authorization and settlement
  5. View the authorization/settlement as well as the funding transactions
  6. Adjust the available credit

Remember that the CV environment runs on Galileo system time.

Set up the products

Work with Galileo to set up your CC funding and CC spending products in CV. Galileo recommends that you configure all of the settings that you intend to use in Production.

CC funding product

At minimum, the funding product should have these characteristics:

  • Product otype 0
  • Product category 32

CC spending product

At minimum, the spending product should have this characteristic:

  • Product category 33

Create the accounts

Follow these steps to create a CC funding and a CC spending account.

Create the CC funding account

  1. Call Create Account with these parameters:
ParameterValue
firstNameCC Funding
lastNameAccount1
prodIdCC funding product ID
businessNameRequired if prodId is a business product.
  1. In the response, capture the pmt_ref_no (PRN) for future use.

Activate the CC funding account

  1. Check the status of the CC funding account by calling Verify Account with this parameter:

    • accountNo: PRN of the CC funding account
  2. If the account_status is not N, activate the CC funding account by calling Modify Status with these parameters:

ParameterValue
accountNopmt_ref_no of the CC funding account
type1

Set the credit limit on the funding account

To set the credit limit on the CC funding account, call Set Corporate Credit Limit with these parameters:

ParameterValue
accountNopmt_ref_no of the CC funding account
amount1000

Create a CC spending account

  1. Call Create Account with these parameters.
ParameterValue
firstNameJane
lastNameSchmidt
prodIdCC spending product ID
businessNameRequired if prodId is a business product.
fundingAccountNopmt_ref_no of the CC funding account
  1. Capture the these values from the response:
    • pmt_ref_no
    • card_id (CAD)
    • Last four digits of card_number
    • expiry_date
    • card_security_code
  2. As desired, create a second CC spending account, such as a card with a different CC spending account product ID.

Activate the spending card

  1. After creating the CC spending card, call Activate Card with these parameters (See Card activation in Setting Up a Card Program for information about other activation options.):
ParameterValue
accountNoPRN or CAD of the CC spending account
cardExpiryDateexpiry_date as YYYY-MM
cardSecurityCodecard_security_code (In CV it is always 123)
cardNumberLastFourOptional. Last four digits of card_number. If there is more than one card associated with the PRN, you must populate this parameter.
  1. To verify that the card has been activated, call Get Card with the PRN or CAD of the card for accountNo. Inside the embossed_cards object you should see status: N.

View account relationship

To see the relationship between the CC funding and CC spending accounts, call Get RTF Account Relationship with this parameter:

  • accountNo: PRN of the CC funding account, which returns all of the spending accounts that are associated with it.

Alternatively, you can call the endpoint with a CC spending account PRN for accountNo to return the associated CC funding account.

Perform transactions

  1. To simulate a simple card transaction in CV, call the Create Simulated Card Authorization endpoint with these parameters:
ParameterValue
accountNoPAN or CAD of the CC spending card
amount10
associationmc_auth
merchantNameCentral Market
currencyCodePopulate this parameter only when the currency of the program is not 840 (U.S. dollar): 124 (Canada), 484 (Mexico), or 170 (Colombia).
  1. Capture the auth_id for future use.
  2. Settle the transaction by calling the Create Simulated Card Settlement endpoint with these parameters:
ParameterValue
accountNoPAN or CAD of the CC spending card
authIdThe auth_id from the previous endpoint response.
associationmc_auth
amount10 or blank

View the CC transactions

To see the transactions that were created, call Get All Transaction History twice:

  1. accountNo — PRN of the CC funding account
  2. accountNo — PRN of the CC spending account

For the CC spending account you should see four transactions. The auth_id and source_id are example values only.

trans_codeamtauth_idsource_idcalculated_balance
ADSY102222444510
AUA-10222222220
BO510None222210
SE5-10222222220

For the CC funding account, you should see one transaction.

trans_codeamtauth_idsource_idcalculated_balance
ADFY-1022224444-10

Check the credit limit

For the funding account, call Get Corporate Credit Summary. This should be the result:

  • available_credit: 990
  • credit_limit: 1000

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.

Pay off the balance

For the CC funding account, call Get Balance. This should be the result:

  • balance: -10

That is the amount owed on the CC funding account. To pay it off, you can apply the funds to either the spending account or the 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 CC spending account with these parameters:

ParameterValue
transactionIdAny unique 64-bit integer. In Postman you can use the {{$randomInt}} variable. (This is only for the Create Adjustment endpoint. All other endpoints can use a UUID or other format.)
accountNoPAN or PRN of the CC spending account
amount10
typeRL
debitCreditIndicatorC
includeRtfTransfer1 or blank so that the funds will be automatically moved to the funding account.

Alternatively, you can use Create Payment to apply the funds, using the same type.

Add funds to the funding account

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 CC funding account with these parameters:

ParameterValue
transactionIdAny unique 64-bit integer.
accountNoPRN of the CC funding account
amount500
typeRL
debitCreditIndicatorC
includeRtfTransfer0 so that the adjustment will not affect the spending accounts.

Call Get Corporate Credit Summary for the funding account. This should be the result:

  • available_credit: 1500
  • credit_limit: 1000

The available credit is higher than the credit limit by 500.00. The spending cards now have a 1500.00 spending limit, without your needing to change the credit limit.

Alternatively, you can call Set Corporate Credit Limit to set the credit limit to 1500.00 or any other limit.

Simulate a Visa transaction

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

📘

Note

For other types of transactions, see the Simulating Card Transactions guide.



Galileo Financial Technologies, LLC 2024

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of Galileo Financial Technologies, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of Galileo Financial Technologies, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.