Stax
Import your merchants and their transaction history from Stax into Preczn.
Import your merchants and their transaction history from Stax into Preczn.
Stax is a data import connection. Preczn reads merchant records and historical transactions from your Stax account and creates matching records in the merchant vault — it does not route new transactions to Stax.
Stax does not process payments through PrecznA Stax connection cannot be added to a plan and will not accept a transaction. Use it to bring existing Stax merchants and their history into Preczn, then route new volume to a processing connection. See Supported Connections for connections that accept transactions.
Supported Capabilities
| Capability | Status | Notes |
|---|---|---|
| Merchant Import | Supported | Business details, owners, and banking from Stax merchant records |
| Historical Transaction Import | Supported | Card and bank transactions with their original status |
| Payment Processing | Not supported | Transactions cannot be routed to Stax |
| Merchant Onboarding | Not supported | Merchants sign up with Stax directly |
Adding Platform Credentials
Stax issues one API key to your platform. It is stored on the platform's Stax connection and is used for every import.
| Credential | API field | Description |
|---|---|---|
| API Key | secret | The Stax API key, sent as a bearer token on each request |
Add it to the platform's Stax connection — see Connection Configuration.
Sandbox and production keys are not interchangeablePreczn checks that the key's environment matches the mode it is configured in. A sandbox key saved in Live mode fails verification, and a production key saved in Test Mode fails the same way. Configure each mode with the matching key.
Adding Merchant Credentials
A merchant created by the import already carries its Stax merchant ID. To link an existing Preczn merchant to a Stax record manually, supply that ID.
| Credential | API field | Description |
|---|---|---|
| Merchant ID | mid | The merchant's ID in your Stax account |
Enter it on the merchant's Stax connection in the Dashboard, or send it as mid to the connection update endpoint — see Linking Existing Credentials. Preczn verifies the merchant ID with Stax before saving it.
Merchant Import
Preczn pages through every merchant in your Stax account and creates a Preczn merchant for each one, pulling both the merchant record and its registration data.
What Gets Imported
Preczn imports the merchant's full profile as Stax holds it, so the resulting Preczn merchant record is populated rather than a stub:
- Business profile — identity, contact details, addresses, industry classification, and the business and volume details Stax holds on the merchant.
- Ownership — the principal owner on the merchant's registration, plus any additional representatives Stax has on file.
- Banking — the merchant's settlement account details.
- Terms of service — the acceptance record Stax captured, carried onto the Preczn connection.
Fields that Stax leaves empty, or that fail validation on the way in, are skipped rather than blocking the import.
Need the field-level list?Contact Preczn support for the exact set of fields imported from Stax and where each one lands on the Preczn merchant record.
Connection Status
The imported connection takes its status from the Stax merchant's status:
| Stax status | Preczn connection status |
|---|---|
ACTIVE | Active |
PENDING | Pending |
INACTIVE | Closed |
Any other value is also recorded as Closed.
Historical Transaction Import
Preczn imports transactions for the merchants it has matched to a Stax merchant ID, pages through the results, and creates a Preczn transaction for each one.
Import Window
The default window is the last 6 months. An explicit start and end date can be supplied instead, and a request for fewer than one month falls back to 6. Stax reports timestamps in Eastern time, and Preczn converts them when the window is applied.
Transaction Types
| Stax type | Preczn type |
|---|---|
charge | Sale |
pre auth | Auth |
capture | Capture |
refund | Refund |
void | Void |
A transaction of any other type is imported without a type.
Payment Methods
Card and bank transactions are both imported, and Preczn records the payment method details from each. A transaction with any other method is imported without payment method details.
FAQ
Can I route transactions to Stax?
No. Stax is an import-only connection in Preczn — it brings existing merchants and history in, but new transactions cannot be routed to it. Route new volume to a processing connection; see Supported Connections.
Where do I find the Stax API key?
In your Stax account. Preczn needs a key for each mode you use, and the key's environment must match — see the warning under Adding Platform Credentials. A merchant who cannot locate their key should ask their Stax representative; Preczn cannot retrieve it.
Why did my API key fail verification?
The most common cause is an environment mismatch: a sandbox key saved against Live mode, or a production key saved against Test mode. Preczn checks the key's environment against the mode and rejects it if they differ. Confirm which environment the key belongs to in Stax, then save it in the matching mode.
How far back does the transaction import go?
Six months by default. A specific start and end date can be supplied to import a different window.
Can I board new merchants to Stax through Preczn?
No. Preczn reads merchants that already exist in your Stax account. Merchants sign up with Stax directly, and the import brings them into Preczn afterward.
What happens to a Stax merchant whose status isn't Active?
It is still imported. A PENDING Stax merchant becomes a Pending connection, and an INACTIVE one becomes Closed, so the record and its history are available in Preczn either way.
Updated about 15 hours ago
