PCI Compliance (or the Payment Card Industry Data Security Standard) is an information security standard for organizations that handle branded credit cards. The PCI Standard is mandated by the card brands but administered by the Payment Card Industry Security Standards Council.

No matter the size of your business, you must comply with PCI standards. They are put in place to ensure all companies maintain a secure environment to take credit card transactions and reduce the risk of fraud.

A payment processor communicates transaction information between the business, the issuing bank, and the acquiring bank. Companies use payment gateways as a tool for e-commerce or card-not-present transactions. In other words, it is essentially a point-of-sale terminal for online transactions. Another distinction between them is that the payment gateway transmits the buyer’s and seller’s approval or disapproval of the transaction. It is the payment processor who initiates the transaction.

Tokenization replaces sensitive data with a randomly generated string of characters that can be linked back to the original data only by an authorized party.

There are three different levels of data:

Level 1 data is standard with all transactions and refers to business-to-consumer (B2C) transactions. It includes basic information like the card number, expiration date, and CVV code. Many require the zip code, merchant name, transaction amount, and amount needed.

Level 2 applies to corporate, commercial, government, and B2B transactions. This level requires all of the Level 1 data and may require the following information:

· Sales Tax
· Sales Tax Indicator
· A Customer Code
· Purchase ID
· Purchase ID Format

Level 3 is typically for substantial transactions and requires more detailed information, including summary data and line detail information.

The credit card company may also ask for:

· Level 1 and Level 2 Data
· Destination Country Code
· Shipping/Courier Charges
· Discount Details
· Order Date
· VAT Information/Reference Number
· Country Code Destination
· Zip Code for Delivery

Level 3 line entry information required consists of:

· Level 1 and Level 2 Data
· Commodity and Product Codes
· Unit Cost
· VAT Details
· Quantity
· An Item Description

Typically, you’ll have 15-20 fields – regardless of the credit card company. There are even some cases where there may be around 100 different fields. Submitting this additional information is required to qualify for Level 2 or 3 interchange fees. But this isn’t always easy for the retailer to uncover. The reason? Most terminals don’t automatically prompt the merchant for the information. Gathering this extra data need not be challenging as long as your provider offers B2B credit card processing. As such, they’ll pass this data along to you.

Replication issues fall into two general categories:

Problems accessing the local database or problems uploading.

If the issue is with the local database, Replication will notify you if it cannot access it.

Verify if anything has changed on your local network and if the SQL account that Replication is using is still active.

If the issue is on the upload side, Replication will run as usual until that point. Replication will use a secure connection if you are uploading to your website.

Verify your SSL certificate is active.

If you upload a Replication OneView job, the issue is likely an IP restriction.

Contact Support for further guidance.

Errors from credit card modules can vary across gateways.

We request the complete error log for further diagnosis.

You can locate all your error logs and send them to Support (support@conligo.ca) by opening any of our modules and clicking the ‘About’ button in the bottom left-hand corner.

An ‘About’ box will open.

Click the Conligo logo, and Windows Explorer will open on your Sage Shared Data directory.

You will see the ‘Logs’ folder.

Open it to find the log you are looking for.