Quantum ePay

Connect your merchant's Quantum ePay account to process credit card transactions through Preczn.

Quantum ePay is a direct processor: each merchant holds their own Quantum ePay terminal, and the three Quantum ePay credentials are stored on that merchant's connection in Preczn. There is no platform-level Quantum ePay connection and no merchant boarding — a merchant must already have a Quantum ePay account before it can be connected.

Supported Capabilities

Supported Transaction Types

Adding Merchant Credentials

Quantum ePay requires three values, all from the merchant's Quantum ePay account. All three are required — a connection saved without any one of them is rejected.

Enter them on the merchant's Quantum ePay connection in the Dashboard, or send them to the connection update endpoint — see Linking Existing Credentials. Preczn verifies all three with Quantum ePay before saving them: the Client ID and Client Secret must authenticate, and the Terminal Key must then be accepted.

📘

There is no merchant ID field

Quantum ePay identifies the account by its Terminal Key, so no separate merchant ID is needed. If you are migrating configuration from another processor, the Terminal Key is the value that plays that role.

Processing Transactions

Route transactions to Quantum ePay the same way as any other connection — through a plan or a direct connection reference on the transaction. The sections below cover the behavior specific to Quantum ePay.

Settlement Timing

Quantum ePay decides every transaction on the API response. A transaction is A (Approved), D (Declined), or E (Error) by the time the request completes — it never sits in P (Pending) waiting for a later update, and there are no status callbacks to configure.

Verify and Card Checks

A Verify on a Quantum ePay connection runs as a zero-dollar authorization, so it validates the card without moving money and without a capture to reverse.

Captures and Refunds

Captures and refunds may be for the full amount or a partial amount.

AVS and CVV Results

Quantum ePay returns AVS and CVV results on sale, auth, and verify. Send the billing street address and postal code to get a meaningful AVS result, and the CVV to get a card-code result. Quantum ePay distinguishes a full address match from a partial one, so a partial result is possible.

Value Limits

Quantum ePay caps the length of several fields, and Preczn shortens them rather than letting the transaction be rejected:

The full values stay intact on the Preczn transaction — only the copy sent to Quantum ePay is shortened.

⚠️

The 16-character statement descriptor is the one to design around

A merchant name longer than 16 characters reaches Quantum ePay cut short, and the statement descriptor is what the cardholder sees on their statement. Choose a descriptor that is recognizable within 16 characters rather than letting it be truncated mid-word.

Data Not Sent to Quantum ePay

Quantum ePay's API has no equivalent for the following. Preczn accepts them and uses them elsewhere, but they never reach Quantum ePay:

• Level II and Level III data — tax, freight, duty, and line-item detail

Preczn does forward the cardholder name, billing address, shipping address, email, and the originating IP address with each transaction. Country codes are converted to the two-letter form Quantum ePay expects, so submit them to Preczn in its standard three-letter form.

Declines and Errors

A transaction Quantum ePay or the issuer rejects is D (Declined) — including a decline for insufficient funds or an amount above the terminal's limit — with Quantum ePay's own message on processorMessage and its code on processorCode. Anything else is E (Error): a connectivity problem, or a request Quantum ePay could not process. The distinction matters for retry logic: an Error is worth retrying, a Decline is not.

Testing in the Sandbox

1. Add the merchant's Quantum ePay connection in Test Mode using their Quantum ePay sandbox Terminal Key, Client ID, and Client Secret.
2. Send transactions using the standard Preczn test cards.

To exercise declines and specific result codes against Quantum ePay, ask Quantum ePay for the sandbox values that trigger them.

Test and Live connections are configured separately, and Preczn routes each transaction to the matching Quantum ePay environment based on the mode it runs in.

FAQ