Devices overview

Payabli supports card-present, in-person payments through physical devices that capture card data at the point of sale. Devices fall into two API categories: cloud devices, which use the cloud payment method, and AXIUM devices, Payabli’s semi-integrated line, which use the device payment method.

Point-to-point encryption

Payabli’s card-present devices encrypt cardholder data at the point of capture using point-to-point encryption (P2PE).

P2PE provides the most secure and effective solution to protect sensitive cardholder data in combination with EMV and tokenization. P2PE can help reduce the cost and scope of PCI DSS and PA-DSS. Encrypted cardholder data has no value if stolen, as only Payabli and secured providers can decrypt the data.

P2PE ensures that no cardholder data is exposed during a transaction by encrypting the data inside the card reader, terminal, or payment device. This encryption makes the data useless in the event of a skimming attack. Using the payment industry standard encryption algorithm, Derived Unique Key Per Transaction (DUKPT), a key is injected securely into each card reader or payment device when it’s manufactured. This key is then used to encrypt every transaction. Each transaction remains encrypted until received by Payabli, where it’s decrypted, then passed to the bank or processor for authorization via Payabli’s secure payment gateway.

1. At the point of card acceptance, within the card reader or payment device, the card data is securely encrypted.
2. After the data is encrypted, it can then be passed over standard public networks to the payment gateway and processor.
3. When the data arrives in the secure data zone of Payabli’s PCI DSS certified payment gateway, it’s decrypted and passed to the bank processor for authorization.

There are numerous benefits to using P2PE devices:

• Easy integration through the use of Payabli’s Cloud Device API
• Reduce scope, complexity and compliance cost of PCI DSS
• Simplified PA-DSS for equipment manufacturers
• Mitigate the risk of cardholder data fraud
• Reduce financial liability
• Reduce software development cost
• Increased cardholder data protection
• Simplified payment processing architecture

Getting started

Find your device family, then follow its guide:

Each family’s guide covers registering, listing, and charging the device through the API. Each device category uses its own payment method:

• Cloud devices (PAX and Ingenico Link and Lane terminals) use the cloud payment method.
• AXIUM semi-integrated devices use the device payment method.

To charge a card, send a transaction with paymentMethod.method set to cloud or device for your device’s category — see Make a sale transaction with the API for the full request and response. For AXIUM, the AXIUM devices quickstart walks you from an unregistered terminal to your first card-present sale.

You can also take card-present payments from the Payabli Portal’s Virtual Terminal — see Create a transaction (Portal).

Related resources

See these related resources to help you get the most out of Payabli.