11/16/2026 Release

This release sends the merchant's voided check to Rainforest during boarding, alongside earlier checks on Payflow Pro credentials, a formatted support phone number in the boarding form, and fixes for merchants with more than 50 locations and for the Merchant Vault's custom date filters.

Jump to: New Features · Improvements · Bug Fixes


New Features

Voided checks for Rainforest boarding

Preczn now sends the merchant's voided check to Rainforest as part of boarding, so Rainforest can verify the merchant's bank account from the document you already collected.

  • Ask for the voided check on Rainforest templates. Rainforest requirement templates now accept voidedCheck in documentRequirements. It's optional by default. When you mark it required, boarding waits for a voided check on each of the merchant's bank accounts.
  • Preczn sends the check before it submits the application. Preczn uploads the voided check for the merchant's primary bank account and attaches it to the application's bank account verification. If the merchant has no voided check on file, boarding continues as before.
  • This applies whether or not your template requires the check. Any Rainforest merchant that already has a voided check on file goes through the upload.
  • Boarding stops when the upload fails. Preczn doesn't submit the application without a voided check that's on file. The connection moves to Error, and its actionDescription says what to do. For example: "Rainforest couldn't accept the voided check. Upload a PDF, JPEG, or PNG up to 5 MB." or "Voided check not sent to Rainforest: the upload failed. Retry boarding."
  • Use a clear, unprotected file. Rainforest accepts PDF, JPEG, or PNG files up to 5 MB. Password-protected files are rejected.
  • Preczn sends only the voided check. This change doesn't send any other document type to Rainforest.

Improvements

Payflow Pro credentials

  • The API rejects characters that Payflow prohibits. PATCH /v1/merchants/{merchantId}/connections/{connectionId} now returns 400 when a Payflow Pro credential contains = ' - ; < > or a line break, so Preczn never sends Payflow a value it would refuse. The message names the field by its Payflow name, for example Payflow Pro Vendor can't contain these characters: = ' - ; < > or a line break.
  • The Dashboard checks the same characters. On a Payflow Pro connection's Connection details, a credential with a prohibited character shows "Can't contain these characters: = ' - ; < > or a line break." and Verify connection and Save changes stay unavailable until you fix it.

Boarding form

  • The support phone number is formatted. The help window and the PCI questionnaire error now show a North American support phone number, 10 digits or 11 digits starting with 1, as (NNN) NNN-NNNN. The form shows other numbers as you entered them on the template.

Bug Fixes

Boarding form

  • Every location loads for merchants with more than 50. The Business Location, banking, Jack Henry ACH Setup, and review steps now show all of a merchant's locations.
  • Screen readers announce the ACH limits card as not started. Until the merchant answers "Do all locations use the same limits?", screen readers hear "ACH limits by location, not started".

Dashboard

  • An empty custom date no longer filters the Merchant Vault to today. In the Merchant Vault, applying Custom with no date on the Merchant Updated or Connection updated older than filter now leaves that filter off.