Top 5 FAQs Developers Have During the Payment Integration Process

Even with a simple payment API, the integration process can raise many questions. Here are the top five most common questions developers ask us during the integration process.

1. How do you minimize PCI compliance requirements?

PCI scope is defined as all system components that are connected to or included in the cardholder data environment. This includes:

• Applications
• Firewalls
• Networking and computer devices
• Switches and routers
• Servers

It takes full-time dedication and expertise to architect and maintain a payments environment that meets the vigorous requirements of the PCI Security Standards Council. That’s why software providers and developers entrust us with their payment solutions. We build, validate, and maintain PCI compliant payment solutions so you don’t have to!

The PURE Processing Platform has a suite of scope-reducing products and services that remove the value and accessibility to cardholder data, thus eliminating the risk.  Our scope reducing solutions include point-to-point encryption (P2PE), hosted payments and tokenization.

2. Do you offer a RESTful API?

Yes. We are all about flexibility which is why our RESTful payment API is one of our most popular APIs that software developers choose to use when integrating to our payment gateway.

3. What semi-integrated device options do you have for card present transactions?

We offer a wide variety of hardware devices. We have both multi-lane devices and simple terminal options that offer the flexibility you need to address the needs of a variety of clients, from small businesses to multi-location organizations.

4. Is it possible to set up recurring payments for both credit card and ACH transactions?

Yes, you can set up recurring payments for either payment method using our Recurring Payment Web Service. Recurring payments can be set up with various billing periods (i.e. daily, weekly, monthly, yearly, etc.).  All cardholder data is securely stored using Paragon’s PURE^SM Tokenization.

5. What is the difference between an authorization and a sale?

• An “authorization” transaction is a pre-approval for goods or services that will be processed after an order has been fulfilled. Funds are held until the sale transaction is approved or expires.
• Merchants use a “sale” transaction type for the immediate purchase of goods or services. It encompasses both the authorization and capture components in one transaction request.

Have more questions?  We are always here to chat. Contact us to learn more about the integration process using our simple payment API’s.