Creating Corporate Credit Accounts

This guide explains how to use the Create Account endpoint to set up Corporate Credit funding and spending accounts. Along with this guide, you might want to read these other guides:

• Corporate Credit — Explains what Corporate Credit is and provides some use cases.
• Testing Corporate Credit — How to test Corporate Credit in the CV environment.
• Corporate Credit Transaction Examples — How various Corporate Credit transaction types look in the ledger.

Create a Corporate Credit funding account

To create a Corporate Credit (CC) funding account, call the Create Account endpoint. Do not use any other endpoint. Go to Creating an Account for general instructions on populating the call and consult the table below for information specific to Corporate Credit accounts.

A CC funding account must be in status: N to fund CC spending accounts. However, the non-active statuses may permit ACH transfers and manual adjustments into or out of the CC funding account. Consult Account Statuses to see what each status permits.

Set the credit limit on a funding account

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

When you want to change the credit limit on the funding account, use this same endpoint.

Create a Corporate Credit spending account

You have these options for creating a CC spending account:

• Begin enrollment with the Start Enrollment endpoint, then create the account and card with the Complete Enrollment endpoint. Use this method when you are using Galileo's integrated customer ID verification and you do not want to create an account until after the cardholder's identity has been verified.
• Call the Create Account endpoint. Use this method for most cases. Go to Creating an Account for general instructions on populating the call, especially if using Galileo CIP, and consult the table below for CC spending-specific information.

Managing Corporate Credit

Although CC accounts have many similarities with conventional accounts, there are some differences, as shown in the sections below.

Viewing Corporate Credit accounts

When you create a CC funding account or a CC spending account, that account will be included in the Customer Master RDF. Only the spending account is included in the Account Card RDF. However, there is no field in those RDFs to link the spending and funding accounts.

To see which CC funding account is associated with a CC spending account, you have these options:

• Retrieve the funding account's PRN with the Get RTF Account Relationship endpoint.
• Capture the funding account's PRN in the fund_pmt_ref_no field in Events API webhook messages.
• Consume the B2B Customer Master Supplemental RDF, which lists each CC spending account and shows the CC funding account that it is associated with.

To see which CC spending accounts are associated with a CC funding account, you can either:

• Use the Get RTF Account Relationship endpoint.
• In the CST, on the CC funding account page, at the bottom of the left navigation, expand the Corporate Credit tab and select Related Spending Accounts.

To check the credit limit or balance of a CC funding account, you can:

• Capture the fund_pastotb value in the Events API webhook messages. This field shows the balance on the funding account.
• View the remaining limit on the CC funding account's landing page in the CST.
• Call the Get Corporate Credit Summary endpoint with the PRN of the CC funding account as the accountNo. This endpoint retrieves both the balance and the available credit.

Viewing Corporate Credit transactions

To identify the transfers between the CC funding account and CC spending accounts, Galileo has created these otypes (transaction types). All transfers are adjustments (act_type: AD). The type (otype) and type_description fields in the table below are from the Get All Transaction History endpoint response.

The CC funding transactions are visible as follows:

• Program API response — Get All Transaction History returns all funding transfers as well as authorizations and settlements. Other endpoints that return transactions (Get Transaction History, Get Authorization History, Get Account Overview) return the authorizations and settlements for CC spending accounts but not the funding transactions.
• CST — The All Transactions screen displays all transactions, including adjustments..
• Posted Transactions RDF — The Base RDF contains the funding transfers as well as settlements.
• B2B Customer Master Supplemental RDF — Lists spending accounts with the associated funding account.
• gAnalytics

Paying off Corporate Credit balances

When paying off the balance of a CC funding account, you must move actual funds into the account. You can use any of these methods:

• Move funds into the funding account using ACH.
  • To initiate transfers from the external account, use the funding account's routing number and PRN to set up the ACH credit.
  • To pull funds from the external account, add an ACH account using the funding account PRN for accountNo. Depending on the type of external account, you can create a corporate ACH account or a regular (personal) ACH account.
  • Use Create ACH Transaction to create an ACH debit. The transfer could take 2–3 days.
• Transfer funds from another account in your program using the Program API. In cooperation with Galileo, you should create a special otype (transaction type) for transfers into a CC funding account.
  • Create Account Transfer — See Creating an Internal Transfer for instructions.
    • The sending account must have the same prog_id as the CC funding account. If it does not, you must set program parameters to permit transfers between the program IDs
  • Create Payment — See Creating a Payment for instructions. You must first set up a dedicated sending account for this endpoint.
  • Create Adjustment — See Creating an Adjustment for instructions. It is not necessary to set the includeRtfTransfer parameter for this kind of transfer.

Setting authorization limits on Corporate Credit accounts

When you set up your CC spending product, you set velocity limits for the product (amount per transaction, amount per week) as well as MCC and merchant ID limits. To set these same limits on a per-account basis, use Galileo's Account-Level Authorization Controls.

On the CC funding product you can set up limits for ACH and Program API transfers.

Adjusting spending account balances

The Galileo system is designed to automatically move funds between the CC spending account and the CC funding account. However, in some rare cases, it is possible that a non-zero balance remains in the CC spending account.

To adjust the CC spending account back to zero, use the Create Adjustment endpoint with includeRtfTransfer: 0 so that the CC funding account is not affected. You may want to request that Galileo create a type that indicates a purely administrative adjustment, or you can choose from among the otypes that you already have.

Reissuing or replacing spending cards

The reissue and replacement processes for Corporate Credit spending cards (including lost or stolen) are identical to the conventional procedures but with one exception: because the spending account always has an available balance of zero, attempting to assess a card-replacement (REP) or card-reissue (REI) fee will fail, which causes the reissue or replacement process to prematurely stop.

To address this issue, set the RINFP parameter on the spending card product, which assesses the fee on the funding account. Keep in mind that these fees are assessed even when the credit limit will be exceeded.

Closing a corporate credit spending account

You can close a CC spending account the same way that you close a conventional card account, using Modify Status. If you select a type that closes related accounts, the CC funding account is not affected.

Closing a corporate credit funding account

When you close a CC funding account, all of the associated CC spending accounts become unusable—all authorization requests are denied because the cards have no available credit by themselves.

🚧

Warning

You cannot migrate CC spending accounts to a different CC funding account.

To close a CC funding account, call Modify Status with the desired type:

• 2 — Change status to D (deactivated)
• 13 — Change status to C (canceled)
• 16 or 20 — Change status to Z (canceled without refund)

Events API webhooks

The same Authorization Events and Settlement Event webhook messages are sent for the CC spending account transactions as for conventional transactions, such as BAUT: auth, DAUT: denied_auth, and SETL: setl.

However, you will have new fields enabled for those messages:

• fund_pastotb_adj — The available balance in the funding account, after the current transaction has taken place. This field is not available for denied authorizations.
• fund_pmt_ref_no — The PRN of the CC funding account that is associated with the CC spending account.

No event webhooks are sent for the transfers between the CC funding account and the CC spending accounts.

Corporate Credit accounts and other Program API endpoints

The behavior of some other Program API endpoints is slightly different with CC accounts:

• Get Related Accounts — Cannot be used to show the relationships between CC funding and CC spending accounts; instead, use Get RTF Account Relationship.
• Add Account — Cannot be used to create a CC funding account. Can be used to create a CC spending account or to add accounts to a CC spending account, but the balance cannot be shared.
• Switch Product — The prodId must be another product of the same type, so a CC funding account can be switched to another CC funding product. If an invalid switch is attempted, the endpoint returns status_code: 590-02 (Product cannot be switched to an unauthorized product).
• Add Card — Cannot be used to add cards to a CC funding account. Can be used to add a card to a CC spending account.
• Modify Status — Some of the values of type have different behavior with CC accounts:
  • A type such as 2, 13, 16 or 20 cancels a card and/or its account, plus related accounts. When a CC spending account is canceled in this manner, the CC funding account is not affected.
  • A type that affects cards, such as reissue, freeze/unfreeze or lost/stolen, cannot be used on CC funding accounts.
• Get Account Overview, Get Transaction History — For a CC spending account, only the authorizations and settlements are returned, as well as conventional payments and adjustments. The CC funding transactions are not returned. For a CC funding account, all of the funding transfers (FY, FZ) are returned as well as other payments and adjustments.
• Get All Transaction History — For a CC funding account all funding transfers (FY, FZ) are returned as well as other payments and adjustments. For a CC spending account, all transactions including the funding transfers (SY, SZ) are returned.
  • For all three transaction-retrieval endpoints there is a custom field in the response, depending on whether the accountNo is a CC funding or CC spending account:
  • spending_account_prn — Contains the PRN of the associated CC spending account for FY and FZ transactions.
  • funding_account_prn — Contains the PRN of the associated CC funding account for SY and SZ transactions.