This article explains how LoanPro works with issuing processors to identify ATM and cash withdrawal swipes. It also covers how qualifying transactions are automatically routed to the designated cash advance bucket.

Cash advance bucket

Before you can route cash advances to a bucket, you need to create a new bucket or use a pre-existing one. To create a new bucket, follow these steps:

1. Navigate to Programs > select a program > Finance Charge & Transactions > Buckets.

2. Click the ‘New Bucket’ button in the upper right side of the page.

3. Choose a bucket type, then complete the setup wizard.

• Note: We recommend naming the bucket “Cash Advance” so it is easy to identify.

To route cash advances to your new bucket or a pre-existing one:

1. Within an individual program, access Card Configuration > Cash Advances.

2. Select your desired bucket from the dropdown menu.

3. Click Save Changes.

Transaction routing process

The routing process for cash advances depends on where the swipe is logged.

• If a swipe is created through Secure Payments or an issuing processor, a cash advance flag (cash-advance?) is passed to the LMS. When the flag is set to true, the transaction is routed to the designated cash advance bucket as defined in the card configuration.
  • Note: This requires a pre-existing configuration that specifies the routing bucket for cash advances.
• If a swipe is posted directly within the LMS, choose the designated cash advance bucket when logging it. The bucket ID can then be referenced in API calls.

Issuing processors

LoanPro currently supports three issuing processors for cash advances: Galileo, Lithic, and Visa DPS. The designation of a transaction as a cash advance depends on the issuing processor and how the cash advance flag is set or derived.

Galileo and Visa DPS

Galileo and Visa DPS handle cash advances by:

1. Explicitly identifying a transaction method as cash or quasi-cash (e.g., casino gaming chips, lottery tickets, money orders, traveler's checks, foreign currency exchanges, or cryptocurrency purchases.)

2. Passing the designation to LoanPro’s LMS, which uses it to determine how a transaction is routed.

Lithic

Unlike Galileo and Visa DPS, Lithic does not explicitly identify a transaction method as cash or quasi-cash. Instead, LoanPro hardcodes the cash advance flag on Lithic transactions.

The LMS automatically sets the cash advance flag to true when Lithic processes transactions with the following Merchant Category Codes (MCCs):

• 6010
• 6011
• 6012
• 6050
• 6051

Additional MCCs

The following MCCs should route to your designated cash advance bucket, but they are not currently hardcoded. They may require additional handling or explicit flagging to ensure proper routing.

• 7995: Gambling transactions, which are often treated as a cash advance by card issuers.
• 9702: Visa Global Customer Assistance Services (GCAS) transactions. These emergency support transactions are unique to Visa.

BYOIP integrations

For bring-your-own-issuer-processor (BYOIP) integrations, clients need to explicitly set the cash advance flag (cash-advance?) when creating a swipe through Secure Payments or an issuing processor. The logic used to determine when this flag is set is owned by the system making the API call—either the issuing processor (if LoanPro is in the authorization stream) or the program manager's transaction authorizing system.

How it works:

1. When calling directly into the swipe’s processor, the flag is named cash-advance?.

2. The flag is set to true if the swipe qualifies as a cash advance.

• If the swipe does not qualify, the flag is set to false.

When cash-advance? is true:

1. The cash advance available balance is used during authorization in the processor that handles the swipe.

2. LMS routes the transaction to the designated cash advance bucket for the associated line of credit account.