What Information Will I Need From My Credit Card Processor?

Lavu POS allows for credit card integration via compatible Gateways. It is important to note that each compatible Gateway is integrated with specific credit card swipers and requires different Integration Data to work with Lavu POS. Contact the gateways below for information concerning their fees (Lavu POS charges no fees for credit card integration) and to acquire the Integration Data necessary for credit card integration.

The information below can also be found by:

1.Log into the Lavu Control Panel at admin.poslavu.com.

2. Navigate to Settings > CC Integration.

3. Click the “?” icon to the right of the table header.

FIGURE 1

SPECIAL INFORMATION ABOUT THE GATEWAYS:

Credit card batches run from Batch Settlement to Batch Settlement and do not necessarily line up with the date or the day start/end time. A merchant set up for manual batch settlement may keep a batch open for several days, though it is recommended that the batch be settled at least once a day. In case a merchant does keep a batch open for more than one day and wants to be able to submit tips, all tips for all days must be submitted before the batch is settled in order for the tips to be processed.

For instance, if a batch is left open from August 12th to August 15th, pressing the "Settle Credit Card Batch" while on the End of Day screen for the 12th after submitting the tips for the 12th will settle all the transactions that occurred from the 12th to the 15th, not just the transactions from the 12th. All the transactions from the 12th to the 15th belong to the same batch. The tip adjustments must first be submitted for the 12th, 13th, 14th, and 15th before settling the batch in order for the tips to be processed.

Any clients using Auth as the default transactions must be sure to submit captures for all their transactions each day prior to submitting the batch for settlement. Failure to do so will result in transactions being left off of the batch, and the funds will not be transferred. To ensure that all transactions are submitted for capture each day, the owner or a store manager should go to the All Users detailed End of Day report and click the "Submit Tip Changes / Capture Authorizations" button at the bottom of the page. This action should be included in the daily or nightly routine prior to the daily or nightly batch settlement.

 

PREFERRED GATEWAYS:

--- Vantiv ---

Integration data 1: MERCHANT NUMBER

Integration data 2: WEB SERVICES PASSWORD

Integration data 3: HOSTED CHECKOUT MANUAL ENTRY TERMINAL ID (available with POSLavu version 2.0)

Integration data 4: HOSTED CHECKOUT PASSWORD (available with POSLavu version 2.0)

Integration data 5: leave blank

Compatible Card Readers: iDynamo, uDynamo

The primary merchant account cannot be used to process both keyed-in transactions and End-To-End Encryption (using iDynamo swipes). Keyed-in transactions must then be processed through Vantiv's Hosted Checkout system, which requires a separate set of credentials.

Supports Tip Adjustments (Adjusts) for Sale transactions and PreAuthCaptures for Auth (PreAuth) transactions. The value to use for the default transaction type when a merchant wants to be able to perform tip adjustments may depend upon the processor, merchant service provider, or bank being used by the merchant. Vantiv should advise.

Credit card batch is held by Vantiv's system. The merchant has the option of having the batch automatically settle at a certain time each day or to be manually settled by the merchant at the merchant's discretion. Some processors may not support manual batch settlement.

The batch is manually settled when the back end user presses "Settle Credit Card Batch", at which point a CaptureAll (BatchSummary & BatchClose) is sent to Vanitv.

The Hosted Checkout batch is separate from the primary batch but runs parallel to it, so any manual batch settlement requests will be sent for both when the end user presses "Settle Credit Card Batch". In case the merchant opts for auto batch settlement, the time of settlement should be the same for both batches.

Supports Gift Card integration with POSLavu 2.0+

--- Bridgepay ---

Integration data 1: USERNAME

Integration data 2: PASSWORD

Integration data 3: leave blank

Integration data 4: leave blank

Integration data 5: leave blank

Compatible Card Readers: BlueBamboo MFi P25-M, iDynamo, uDynamo, iMag Pro, LineaPro, Infinea Tab

Supports Tip Adjustments (Adjustments) for Sale transactions and PreAuthCaptures (Force Auths) for Auth transactions. The value to use for the default transaction type when a merchant wants to be able to perform tip adjustments may depend upon the processor, merchant service provider, or bank being used by the merchant. Bridgepay should advise.

Credit card batch is held by Bridgepay's system. The merchant has the option of having the batch automatically settle at a certain time each day or to be manually settled by the merchant at the merchant's discretion. Some processors may not support manual batch settlement.

The batch is manually settled when the back end user presses "Settle Credit Card Batch", at which point a CaptureAll is sent to Bridgepay.

Supports Gift and Loyalty Card integration with POSLavu 2.0+     

--- Heartland ---

Integration data 1: USERNAME

Integration data 2: PASSWORD

Integration data 3: LICENSE ID

Integration data 4: SITE ID

Integration data 5: DEVICE ID

Compatible Card Readers: BlueBamboo MFi P25-M, iMag Pro, LineaPro, Infinea Tab

Supports Tip Adjustments (CreditTxnEdits) for Sale transactions and PreAuthCaptures (CreditAddToBatches) for Auth transactions. The value to use for the default transaction type when a merchant wants to be able to perform tip adjustments may depend upon the processor, merchant service provider, or bank being used by the merchant. Heartland should advise.

Credit card batch is held by Heartland's system. The merchant has the option of having the batch automatically settle at a certain time each day or to be manually settled by the merchant at the merchant's discretion.

The batch is manually settled when the back end user presses "Settle Credit Card Batch", at which point a BatchClose is sent to Heartland.

 

Have more questions? Submit a request

Comments