Till Payments

Connect your merchant's Till Payments account to process credit card transactions through Preczn.

Till Payments is a direct processor: each merchant holds their own Till Payments gateway account, and all four Till credentials are stored on that merchant's connection in Preczn. There is no platform-level Till connection and no merchant boarding — a merchant must already have a Till Payments account before it can be connected.

Supported Capabilities

Supported Transaction Types

Adding Merchant Credentials

Till Payments requires four values, all found in the merchant's Till Payments gateway account. All four are required — a connection saved without any one of them is rejected.

📘

Credential Verification

Preczn verifies Till Payments credentials with the gateway when you save them, so a mistyped value is caught at configuration time rather than on the first transaction. All four values participate: the Username and Password authenticate the request, the API Key selects the account, and the Secure Secret signs it — a wrong Secure Secret fails verification even when the username and password are correct.

⚠️

The Secure Secret is not an environment name

The Secure Secret is submitted in the API field named environment, but it is a signing secret, not a sandbox/production switch. Preczn selects the Till Payments environment from the mode of the connection — a Test Mode connection always reaches the Till sandbox gateway, and a Live connection always reaches production.

Configuration Methods

Till Payments credentials can be configured three ways.

Dashboard

The four values are collected on the merchant's Till Payments connection form, labeled API Key, Username, Password, and Secure Secret.

1. Navigate to Merchants > select merchant > Connections
2. Select Till Payments
3. Enter the credentials as labeled
4. Save the connection

The API Key is masked once saved, so it is not displayed in full when the connection is reopened. To replace credentials on a merchant who already has a Till Payments connection, the API method below is the most direct route.

Merchant Import

Include the credentials when importing merchants via CSV, using these column headers:

API Integration

Configure credentials programmatically with the Update Connection Details endpoint:

curl --request PATCH \
  --url https://api.preczn.com/v1/merchants/{merchantId}/connections/TillPayments \
  --header 'Authorization: Bearer {api_key}' \
  --header 'Content-Type: application/json' \
  --data '{
    "mid": "{API Key}",
    "key": "USERNAME",
    "secret": "{Password}",
    "environment": "{Secure Secret}"
}'

Request Fields

⚠️

No Spaces Allowed

The mid, key, and secret fields cannot contain spaces. Requests with spaces in these fields are rejected.

Processing Transactions

Route transactions to Till Payments 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 Till Payments.

Verify and Card Checks

A Verify on a Till Payments connection is performed 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. A capture references the original authorization, and a refund references the transaction being refunded — Preczn supplies those references, so nothing extra is required on the request.

Stored Credentials and Card on File

When a transaction uses a stored payment token, Preczn tells Till Payments what kind of stored-credential transaction it is, based on the token's usage type:

Single-use tokens and raw card data carry no stored-credential indicator. See Card On File Flags for how usage is set.

AVS and CVV Results

Till Payments does not return an address or card-code verification result on the transaction response, so AVS and CVV are reported as U (unavailable) on approved card transactions. An AVS result is populated later if Till Payments includes one on its status callback.

Preczn still sends the billing address and CVV with every card transaction, so nothing changes about how you build the request — the results simply aren't returned for reporting.

Data Sent to Till Payments

Preczn forwards the cardholder name, billing address, shipping address, phone number, and originating IP address with each card transaction.

Till Payments' API has no equivalent for the following, so these are accepted by Preczn and used elsewhere but never reach Till Payments:

• Metadata
• Dynamic Statement Descriptors
• Level II and Level III data

Asynchronous Status Updates

Till Payments reports the final outcome of a transaction with a status callback. Preczn registers the callback address on every request it sends, so there is nothing to configure in your Till Payments account, and no webhook to maintain.

A transaction can therefore return P (Pending) and settle to A (Approved) or D (Declined) when the callback arrives. Treat P as "not yet an outcome" — subscribe to the transaction.approved, transaction.declined, and transaction.errored webhook events, or poll Get Transaction.

Transaction Status Mapping

A status of E (Error) means the request itself failed — a connectivity problem or a request Till Payments could not process — rather than an issuer decision. Capture, void, and refund requests that Till Payments reports as unsuccessful are also recorded as E, with the gateway's message on the transaction.

Testing in the Sandbox

1. Add the merchant's Till Payments connection in Test Mode using their Till Payments sandbox gateway credentials.
2. Send transactions using the standard Preczn test cards — Preczn translates them to Till Payments' sandbox card numbers automatically, so no gateway-specific test data is needed.

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

FAQ