11/10/2026 Release

This release adds 3D Secure challenges for Stripe card payments and lets the Merchant API reset a connection or change its status on live merchants, alongside a redesigned Jack Henry ACH Setup step in the boarding form, more complete AuthorizeNet requests and errors, and fixes to plan default splits and Transaction Log date ranges.

Jump to: New Features · Improvements · Bug Fixes


New Features

3D Secure for Stripe card payments

You can now ask Stripe to authenticate a card payment with 3D Secure. When the issuer requires a challenge, Preczn returns the transaction as pending and your page opens the challenge in a Preczn-hosted window. To set up the request, the browser SDK, and outcome handling, see the 3D Secure Integration guide.

  • Opt in per transaction. Send requestThreeDSecure on POST /v1/transactions. The default, none, keeps today's behavior.
  • 3D Secure applies to Stripe and StripeConnect card sales and authorizations paid with a single-use token. Preczn ignores requestThreeDSecure for other processors, wallets, raw card data, multi-use tokens, and verifications, and processes the transaction without 3D Secure. The request doesn't return an error in these cases.
  • Confirm the outcome on your server. When the challenge ends, the transaction moves to A or D and Preczn sends the existing transaction.approved or transaction.declined webhook.

Changes for existing Stripe integrations:

  • Verifications approve only cards that Stripe confirms. This applies to every Stripe VERIFY, whether or not you use 3D Secure. A verification returns A when Stripe confirms the card. If the card's issuer requires authentication, the verification returns D, because verifications never run a challenge. If Stripe is still processing the card, the verification returns P.
  • Stripe cancellation events update only the transactions they apply to. A cancellation updates a void, an approved transaction, or a pending 3D Secure transaction. A declined sale or authorization stays declined.

Connection reset and status changes in the Merchant API

The Merchant API can now do two connection actions that were available only in the Dashboard.

  • Reset a connection. POST /v1/merchants/{merchantId}/connections/{connectionId}/reset clears a connection's data and returns it to Unconfigured, on test and live merchants. Use the processor name, such as Payrix, as connectionId. The endpoint needs a private API key, takes no request body, and returns 200 with the merchant. Preczn then re-checks the connection's requirements and sends a merchant.updated webhook.
  • Change a connection's status on live merchants. PATCH /v1/merchants/{merchantId}/connections/{connectionId} now accepts status on live merchants as well as test merchants. Preczn applies the status directly and doesn't enforce onboarding transition rules.
  • The accepted statuses match the Dashboard. status accepts Active, Cancelled, Closed, Disabled, Error, Inquiry, Pending, Queued, RFI, Rejected, Sent, and Unconfigured. Preczn sets Requirements, Ready, Evaluating, Underwriting, and PartialBoarded itself, so this endpoint now rejects them with 400 and status must be one of: Active, Cancelled, Closed, Disabled, Error, Inquiry, Pending, Queued, RFI, Rejected, Sent, Unconfigured. This applies to test merchants too. Update any test script that sets Ready through this endpoint.
  • Every change is logged. API resets and status changes appear in the merchant's activity log as made through the API. Status changes are saved for every connection type, including ones Preczn doesn't board, such as Stripe. Resets that Preczn makes on your behalf also send a merchant.updated webhook.

Improvements

Jack Henry ACH limits

The boarding form's Jack Henry ACH Setup step now collects every location's check and ACH limits in one table, and the form and the Merchant API check that the limits are in a consistent order.

  • One table for all locations. The ACH limits by location table replaces the per-location tabs. Each row shows the location's dollar limits (Single check/ACH, Daily total, Two-week total) and count limits (Daily, Two-week), with a status such as "Complete" or "2 remaining". Below 1024 pixels wide, each location becomes a card.
  • Instructions on the step. A How to fill in this step card defines each limit, and merchants can hide it with Hide instructions. A warning that always stays visible states that any check or ACH payment above a limit is declined.
  • Fill many locations at once. With two or more locations, the step asks "Do all locations use the same limits?" Yes, the same limits shows one row that applies to every location. No, they differ shows a row per location and a Copy to empty link that copies the first location's limits to locations with no limits yet.
  • Limits must increase within each group. Single check/ACH can't exceed the daily total, and the daily total can't exceed the two-week total. The daily count can't exceed the two-week count. Equal values are allowed. A limit of 0 isn't accepted. The form shows "At least" and the lowest allowed value under a field that breaks the rule, and Save & Continue stays disabled until every location is complete.

ACH limits by location

2 locations remaining
Do all locations use the same limits?
Yes, the same limitsNo, they differ
Dollar limitsCount limits
Location*Single check/ACHLargest payment*Daily totalBusiest day*Two-week total14-day period*DailyBusiest day*Two-week14-day period
Main Street Store
Complete
Copy to empty (1)
Fills only locations that have no limits yet.
$5,000
$20,000
$100,000
50
400
Riverside Office
1 invalid
$10,000
$8,000
At least $10,000
$150,000
40
300
Airport Kiosk
5 remaining
 
 
 
 
 
  • The Merchant API enforces the same rule. Location create and update requests on /v1/merchants/{merchantId}/locations and /v1/forms/{formId}/locations return 400 when a Jack Henry connectionData entry has out-of-order limits or a limit of 0. The message names the field, for example connectionData entry for processor 'JackHenry': <field> must be greater than or equal to <earlier field>.

For the rules, the error response, and screenshots of the step, see Locations and ACH limits in the Jack Henry guide.

AuthorizeNet

  • Names and phone numbers reach AuthorizeNet without an address. Card sales, authorizations, and verifications now send the cardholder's first and last name, and the transaction's phone, even when the request has no billingAddress. This supports merchants who mark these fields as required in AuthorizeNet. A verification still needs a billing address and postal code.
  • Line-item prices arrive in currency units. Preczn converts each item's price to the currency's major units before it sends the line item, so a USD price of 1000 is sent as 10. The charged amount is unchanged.
  • Full address matches return avs M. When AuthorizeNet reports that the street address and postal code both match (AVS code Y), authorization.avs is M.
  • ACH account names fit AuthorizeNet's limit. Preczn shortens the ACH name on account to 22 characters, AuthorizeNet's limit. For corporate checking and savings accounts, Preczn sends accountBusinessName as the name on account when the request includes it.
  • Errors carry AuthorizeNet's code. A transaction with status E returns AuthorizeNet's error code in processorCode, such as 290 or E00027. When AuthorizeNet returns no transaction ID, the response omits processorTransactionId.

Transaction API

  • Error responses pass through the processor's error details. When a processor's error response includes an error code or message, Preczn now returns them in authorization.processorCode and authorization.processorMessage on sale, authorization, drawdown, capture, refund, and void responses with status E, as it already did for verifications. Not every processor returns these details, so don't rely on either field being present.

Connections

  • Live Adyen connections require a valid URL prefix. Saving a live Adyen or Adyen for Platforms connection with an empty or invalid urlPrefix returns 400. A valid prefix is Adyen's live URL prefix, which uses letters, numbers, and hyphens, and doesn't start or end with a hyphen. Test connections are exempt. A Merchant API update that omits urlPrefix keeps the stored value.
  • Ramp business descriptions fit Ramp's limit. Preczn sends Ramp up to 250 characters of a merchant's product or service description. A longer description is shortened to 247 characters followed by ....

Merchant import

  • Imports enforce the 50-character external ID limit. When you import merchants from a CSV file on the Import Merchants page, a row whose externalId is longer than 50 characters now fails with externalId must be shorter than or equal to 50 characters. This matches the limit everywhere else you set an external ID.
  • Import errors stay in one column. The import result file lists all of a row's validation messages in its error column, separated by semicolons.

Dashboard

  • A clearer Edit User page. Mode Access is now a Test and Live / Test Only control that shows the user's current access. Only one card on the page can be edited at a time, and the other cards' Edit buttons are disabled until you save or cancel. Password reset shows its requirements as a checklist, and the page shows the full user ID with a copy button.
  • Payflow Pro credentials are checked for prohibited characters. When you add or edit a Payflow Pro connection, the credential fields show "Can't contain these characters: = ' - ; < > or a line break." and block saving until you remove them. A saved Vendor with a dash shows this error when you edit the connection.
  • The Webhook deliveries tab fits the transaction drawer. The deliveries table no longer scrolls sideways. Attempt ID moved from a table column to the top of each delivery's expanded details.

Bug Fixes

Dashboard

  • New plans always get a default split. A plan with at least one card connection now gets a default split regardless of the order in which you select connections. The split covers only card connections, not lending or issuing connections, and uses whole percentages. For example, three connections split 34, 33, and 33.
  • Transaction Log custom ranges filter by the dates you pick. After you choose Custom range, the log searches once you set both Start and End, and it returns only transactions in that range.

Boarding form

  • Expired forms go to the platform's expiration URL. A merchant who opens an expired form now goes to the form's or template's expiration URL instead of preczn.com.
  • Submitted forms record their completion. After Submit, the form waits for its progress update to finish before it redirects, for up to 30 seconds. Each submitted form now records its completion date and sends its completion event.
  • The Business Location step doesn't open address suggestions on its own. The address field no longer takes focus when the step loads, so the suggestion list stays closed until the merchant types.