Credit Card profiles define authorization procedures for credit card sales at your department.
The WebXPress Profile Subtype is designed for use with RecTrac's Electronic Redirect Interface (ERI) with PlugNPay WebXPress.
See Also: Topic Doc - PlugNPay WebXPress.
Making changes to a profile is an Audited Event. Additionally, Linking, Removing, Purging, and Cloning profiles are also Audited Events.
See Also: Topic Doc - RecTrac Profile Assignments Screen, Hierarchy Guide, and Profile Listing.
See Also: Video - Profile Review
Core
User ID (SAProfileDetails_MerchantAccountUserID)
Enter the User ID given to you by PlugNPay, if desired. This is the recommended option.
Leave this field blank to force users to enter this information every time they process a PlugNPay credit card transaction. For obvious reasons this is not recommended.
DeletePayment URL (SAProfileDetails_PaymentURL)
How this field is used is dependent upon your credit card solution. Refer to the entries below.
If you use CardConnect as your Credit Card Solution
Enter the Payment URL as given to you by CardConnect. The URL you enter is dependent your setting in the Hosted Payment Page Version field.
- Hosted Payments V1 - https://securepayments.cardconnect.com/hpp/payment/.
-
Hosted Payments V2 - Enter the URL given to you by CardConnect
See Also: Topic Doc - CardConnect Hosted Payment Page for WebTrac. - Hosted iFrame Tokenizer - N/A. No Payment URL is required.
Note for CardConnect Users: This field is applicable only if you are using this profile for WebTrac payments. If you are NOT using this profile for WebTrac payments then leave it blank.
If you use PlugNPay as your Credit Card Solution - Enter the Payment URL as given to you by PlugNPay. For example https://pay1.plugnpay.com/payment/pay.cgi
DeletePassword (SAProfileDetails_MerchantAccountPassword)
Enter the Password give to you by PlugNPay, if desired. This is the recommended option.
Leave this field blank to force users to enter this information every time they process a PlugNPay credit card transaction. For obvious reasons this is not recommended.
Passwords are masked in RecTrac. Passwords in RecTrac appear either as a series of pipes" or dots in password fields (i.e. | | | | | or •••••).There is no Permission that allows you to see an actual password. There is no Report in RecTrac that will display a password.
Additionally RecTrac user passwords and WebTrac user passwords are encrypted based on the configuration settings as maintained on your Encryption profile.
DeletePayment URL V2 (SAProfileDetails_PaymentURLV2)
Enter the Payment URL V2 given to you by PlugNPay
For Example: https://pay1.plugnpay.com/pay/index.cgi
DeleteAccount Type (SAProfileDetails_AccountType)
Select the type of Account you want to use for this Credit Card profile.
- Normal Retail - Used for normal every day transactions performed in RecTrac.
- e-Commerce - Used for normal every day web-based transactions, such as those performed by patrons in WebTrac.
- Restaurant - Used where credit card transactions will include tip processing, such as in a restaurant or bar.
- MOTO - Used for Installment Billing processed through RecTrac.
ResponseURL (SAProfileDetails_ResponseURL)
Enter the Response URL given to you by PlugNPay
For Example: https://pay1.plugnpay.com/payment/pnpremote.cgi
DeleteSettlement Type (SAProfileDetails_SettlementType)
Select your settlement type for this Credit Card profile.
- Auto - This option settles the transaction with your gateway upon completion. Always use this option for Normal or E-Commerce account types. Use this option for Restaurant account types only if you do not process tips.
- Manual - This option waits to settle the transactions until manually prompted. Select this option only if you are using a Restaurant account type and if you are processing tips, as you want to include the tip in the final settlement.
Card Brands Accepted (SAProfileDetails_WebXPressCardBrandsAccepted)
Click the Combo Box icon to select the Credit Card brands you accept.
DeleteManaged Profiles (SAProfileDetails_ManagedProfiles)
For the PayTrac credit card gateway.
Select the other credit card profiles you want the ability to work with. This controls the records that show in the tip processing program. It does not control the records that display in programs where you can link cards for installment billing household auto pay or tee time no-show. In those programs the records that will display are any "PayTrac" active card on file that was obtained / used for payments in WebTrac.
For CardConnect Elavon/ETS PlugNPay and VeriFone credit card gateways.
Select the other credit card profiles you want the ability to work with during the manual or auto settle process.
DeleteQuery Pause (SAProfileDetails_QueryPause)
Enter a value in this field. The value you enter is the number of seconds RecTrac will wait after the clerk clicks ?Close? before allowing the clerk to process another transaction. This ?pause? will insure the transaction completes on the PlugNPay website.
VSI recommends a value between 1" and "5."
DeleteRequire Signature Amount (SAProfileDetails_SignatureAmount)
How this field is used is dependent upon your credit card solution. In all cases, the value you enter in this field is a threshold value used to determine whether a signature line is printed on the Auth Receipt. Refer to your credit card solution below for more specifics.
CardConnect - The value in this field is involved in determining whether the Ingenico isc250 pin pad prompts for signature or not. It is also used to determine whether a signature line is printed on the Auth Receipt.
- If the isc250 prompts for signature, and the customer signs, then the signature is captured and no signature line will print on the Auth Receipt.
- If the value of the sale is less than the value entered here, the Auth Receipt will print with Signature Not Required."
- For example the isc250 is set to require signature at $25.00. The value in this field is $25.00. A sale of $25.00 or more will prompt for a signature on the isc250 and no signature line will print on the receipt. A sale of $24.99 or less will result in no signature capture on the isc250 and "Signature Not Required" being printed on the Auth Receipt.
Elavon - In RecTrac this the value in this field is used when no signature capture takes place on a pin pad but you want to have the customer sign on the Auth Receipt. For example you do NOT use the Ingenico isc250 pin pad. You want customers to sign for any sale greater than $20.00. You would enter "20.00" in this field. Sale amounts for less than the value entered here will result in "Signature Not Required" being printed on the Auth Receipt.
Note: If using the Ingenico isc250: If you are prompted for a signature and the customer signs then the signature is captured and no signature line prints on the Auth Receipt. If you are not prompted for a signature then "Signature Not Required" prints on the Auth Receipt.
Elavon can make a change on their side to always prompt for signature on the isc250 or to never prompt for signature.
PlugNPayThis field is used to determine whether a signature line will print on the Auth Receipt only. Any sale equal to or greater than the amount entered here will result in a signature line being printed on the Auth Receipt. Any sale less than the value entered here will result in an Auth Receipt with no signature line. For example you want customers to sign for any sale greater than $20.00. You would enter "20.00" in this field.
Note: PlugNPay does not offer pin pads that incorporate signatures at this time.
Query Retries (SAProfileDetails_QueryRetries)
Enter a value in this field. The value represents the e number of times the system will attempt to find a good response from PlugNPay. This number works in conjunction with the Query Pause value in that it will try the number of times you specify but each try will commence when the Query Pause refreshes.
VSI recommends '2.'
Note: If there is no response from PlugNPay or the response for a transaction is a failure (declined) the process looks to the value in this field. If the Query Retries field is set to '0' the transaction is done and there will be no retry in the event of an initial failure. Setting the value to '2' guarantees three (3) tries.
Auth Copies (SAProfileDetails_AuthCopies)
Select the number of credit card/e-Check authorization receipts you want to print upon completion of a transaction. For example, '2' (for two copies): one for the customer, and one to be signed and placed in the cash drawer..
Auth Copies print along with the regular receipt.
DeleteCheck Household for Stored Credit Card? (SAProfileDetails_CheckHHStoredCreditCard)
Select this option to have the system present the clerk with a list of credit cards that a patron/household has used in the past, if any, when processing a transaction and using a Credit Card Payment Code. The clerk can then choose a card from the list, and the last order ID, as well as the masked credit card information will passed to the gateway to validate the sale. If the stored information is verified, the sale will be permitted. If the stored information is not verified, the sale will be declined and a different credit card will have to be used.
Deselect this option if you do not want the system to present a customer's list of previously used credit cards for selection.
Note: The list of credit cards presented contains limited information only (i.e. first digit plus last four (4) digits only). RecTrac does NOT store complete credit card numbers anywhere within the database.
Allow For Partial Authorization Processing? (SAProfileDetails_AllowPartialAuthorization)
Select this option to allow authorizations to be processed for partial amounts of a total sale. Selecting this option allows you to process split payments more accurately, as the process will authorize the credit card total of the split payment only.
For Example: The total sale is $100.00. The customer wants to remit $75.00 via credit card and $25.00 via Gift Certificate. With this option selected, when processing the sale on the PlugNPay website, the authorization check would run for $75.00, or the amount being placed on the credit card. With this option de-selected, the card would have to be authorized for the full amount of the sale regardless of the actual amount being charged.
De-select this option to have all sales authorized for their full amount regardless of whether the full amount is being charged to the card linked to the sale.
DeleteUse StoreData Mode for IB Processing? (SAProfileDetails_StoreDataMode)
Contact VSI prior to selecting or de-selecting this option!
Select this option only if $0 AVS inquiries are NOT allowed by your processor.
DeletePerform Tender Exchange for Tip Processing (SAProfileDetails_PerformTenderXforTipProcessing)
This option is applicable only if you select Restaurant as the Account Type for this profile.
Select this option if you give your servers cash for tips charged to credit cards at the end of their shift.
Leave this option de-selected if servers are given credit card tips as part of their wages or in another form after settlement with the bank.
For example Bobbie Sox finishes her shift and has $100.00 in tips from checks/bills paid by credit card. If you give Bobbie $100.00 from the cash drawer you would select this option. If instead you cut Bobbie a check once your bank has reimbursed you for the credit card sales then you would deselect this option.
DeleteTip GL Code (SAProfileDetails_TipGLCode)
This field is applicable only if you process tips from within RecTrac and is generally restricted to Restaurant Account Types only.
Select the GL Code to which you wish tips to post. This field must be populated in order to gain entry to the Tip Processing program.
GL Codes are maintained in GL Code Management.
DeleteTip Cost Center (SAProfileDetails_TipCostCenter)
This field is applicable only if you process tips from within RecTrac and is generally restricted to Restaurant Account Types only.
Select the Cost Center to which you wish tips to post if desired.
Cost Center Codes are maintained in Cost Center Management.
DeleteDupe Time Adjustment (SAProfileDetails_DupeTimeAdjustment)
Enter a value in this field, if desired. The value you enter represents the time adjustment in hours between your Time Zone and Greenwich Mean Time (GMT)/Coordinated Universal Time (UTC). The Dupe Time Adjustment setting is used to adjust credit card transaction times based on GMT/UTC, so when you run the credit report it will display the correct time.
If you are behind GMT/UTC, like North America, enter a negative value. If you ahead of GMT/UTC, like eastern Europe and Asia, enter a positive value. For Example: Eastern Standard Time is five (5) hours behind GMT/UTC. You would enter -5."
Note: The adjustment does NOT account for Daylight Savings Time. Using the example above Eastern Daylight Savings Time is four (4) hours behind GMT/UTC because you "Spring ahead in the Spring" and set your clocks an hour ahead. You would enter "-4."
Apply/Cancel Message (SAProfileDetails_CustomApplyDupeMessage)
Enter the message that you wish to display in the event your clerk receives an Apply/Cancel option. The Apply/Cancel message will appear when a transaction fails to complete in RecTrac but gets authorized by Your credit card gateway.
VSI recommends using the following message (or something similar):
Choose 'Apply' if the sale failed when processing the credit card during the previous transaction. Clicking 'Apply' will NOT charge the card a second time as it has been authorized for this sale. 'Apply' will use the Your credit card gateway authorization to complete the sale in RecTrac.
"Choose 'Cancel' to cancel this process and return to the payment screen."
For Example a credit card sale fails to complete in RecTrac but the credit card is authorized by Your credit card gateway. At this point RecTrac and Your credit card gateway are not coordinated and the Your credit card gateway report would include this exception. The clerk then attempts the sale again in RecTrac using the same credit card and the same dollar amount. If the credit card number and dollar amount passed to Your credit card gateway match a previous authorization in the Your credit card gateway database then Your credit card gateway passes back the transaction's Order ID to RecTrac. RecTrac then looks to see whether a matching Order ID exists in the RecTrac database. If no matching Order ID is found the system will ask the clerk whether they want to APPLY that Order ID (from the previous Your credit card gateway authorization) to the current RecTrac transaction so that a duplicate credit card authorization is not done on the customer's credit card account. As a result of the clerk APPLYing the Order ID both RecTrac and Your credit card gateway will now be in sync. Optionally the clerk may CANCEL and return to the payment screen.
DeleteForce/Cancel Message (SAProfileDetails_CustomForceDupeMessage)
Enter the message that you wish to display in the event your clerk receives an Force/Cancel option. The Force/Cancel message will appear whenever a clerk attempts to process the same credit card for the same dollar amount, but for a different transaction, within a two minute time span.
VSI recommends using the following message (or something similar):
Choose 'Force' if this a brand new sale to the same credit card for the same dollar amount from a previous sale and you wish to charge the customer a second time."
"Choose 'Cancel' to cancel this process and return to the payment screen."
For Example a patron purchases an ice coffee for $5.00 and remits with a credit card. As that sale is completing the patron asks for a second ice coffee and pays again with the same credit card. When processing the second payment Your credit card gateway will identify that as a duplicate charge (and potential fraud) pass it back to RecTrac and display the Force/Apply Message. This message warns the clerk that the card was already charged and allows them to decide if it should really be charged again.
DeleteVerification Key (SAProfileDetails_PNPVerificationKey)
Input the Hash Verification Key you generated on the PlugNPay Portal into this field. Hash Verification is an additional PlugNPay security feature used to ensure that transactions being sent into PNP have not been manipulated in transit or through use of web development tools.
Refer to the Inbound Verification Hash section of the PlugNPay WebXPress document for further information.
Delete