Changelog
Back to All

9/25/2026 Release

14 days ago by ReadMe API

This release adds a taxExempt flag to transactions with full Level 2 tax data for CardPointe, and moves Ramp merchant boarding to partner authorization, alongside MCC and NAICS pickers that offer the full catalog and clearer AdyenForPlatforms boarding status.

Jump to: New Features · Improvements · Bug Fixes

New Features

Tax-exempt transactions

You can now mark a transaction as tax-exempt explicitly, instead of relying on a zero or missing tax amount to carry that meaning.

  • taxExempt on the transaction request and response. Send taxExempt: true on POST /v1/transactions and Preczn stores it on the transaction and returns it on the response. Preczn never infers exemption from tax: 0; a transaction is tax-exempt only when you say so.
  • Conflicting tax values are rejected. A request that sets taxExempt: true together with a non-zero tax returns a 400.
  • CardPointe is the first processor to receive it. Preczn stores and returns taxExempt on every transaction, but currently sends it only to CardPointe. Support for more processors is coming in future releases.
  • CardPointe receives the complete Level 2 element set. On CardPointe, Preczn now sends the tax-exempt indicator and the tax amount on every authorization, plus a purchase order number taken from the transaction's invoice. Tax-exempt merchants can qualify for Level 2 interchange rates as a result.
  • Know the limits. CardPointe truncates the purchase order number to 36 characters. Captures, refunds, and voids don't carry Level 2 data. CardPointe handles GSA card exemption on its own side.

Ramp merchant boarding: partner authorization

Ramp merchant boarding now runs on Ramp's partner authorization model, so a merchant completes boarding without leaving your flow.

  • No Ramp consent redirect. Merchants no longer bounce out to Ramp to authorize the connection partway through boarding. Preczn authorizes on the platform's behalf, and the Ramp business identifier arrives on the connection once Ramp processes the application.
  • Rejections name Preczn fields. When Ramp rejects a boarding application, the merchant and the connection's action message now name the field in Preczn terms, such as Primary Owner Postal Code, instead of a raw Ramp field path. Problems with the platform's own Ramp connection settings are kept out of the merchant-facing list, since the merchant can't fix them.

Improvements

Dashboard

  • MCC and NAICS pickers offer the full catalog. The MCC and NAICS dropdowns on a merchant's business details and in the boarding-form template editor now list every valid code. The codes your platform configured appear first, under a Recommended heading, rather than acting as a hard filter. If your platform relies on those codes to restrict what users can pick in the dashboard, note that this is now guidance, not enforcement.
  • NAICS search understands plain language. Searching the NAICS picker for what a business does, such as "pizza," returns ranked matches instead of no results.
  • AdyenForPlatforms connections: choose payment methods at creation. The add-connection drawer now includes the same payment-method selection as the edit drawer, so you can enable Affirm when you create an AdyenForPlatforms connection rather than creating it and then editing it.

Bug Fixes

AdyenForPlatforms boarding

  • Account Holder ID is no longer editable. The merchant connection drawer showed Account Holder ID as a required field you could type into. Adyen generates this value during boarding, so the field is now read-only and not required.
  • Boarding stops when Adyen returns no store. If Adyen's response to store creation doesn't include a store, boarding now records the step as failed and flags the connection, instead of continuing without a store or payment methods.
  • AdyenForPlatforms document-upload and PCI-signing failures stay visible. When uploading a merchant document to Adyen fails during AdyenForPlatforms boarding, the error on the AdyenForPlatforms connection is no longer overwritten later in the same boarding run. When signing the Adyen PCI questionnaire fails, the AdyenForPlatforms connection now shows an error, as it already did for a failed Adyen Terms of Service acceptance. Boarding on other connections is unchanged.
  • Adyen PCI questionnaire actions target the right AdyenForPlatforms connection. Listing, downloading, and signing Adyen PCI questionnaires now act on the AdyenForPlatforms connection named in the request.