7/01/2026 Release (Tentative)

This release introduces Greensky merchant boarding and required documents for merchant boarding, standardizes contact phone numbers across the API, and ships a long list of boarding-form, connection, and dashboard fixes.

Jump to: New Features · Improvements · Bug Fixes

New Features

Greensky Merchant Boarding

You can now board merchants onto Greensky directly through Preczn — end to end, from requirements configuration through a complete, guided boarding form.

• Full boarding flow. Greensky merchants move through the same multi-step boarding experience as every other connection — business details, owners, banking, and contacts — with Greensky-specific requirements built in.
• Business Category, partner channel, and contacts are captured and mapped correctly, so applications transmit to Greensky with the data they expect.

Required Documents for Merchant Boarding

You can now require specific documents — such as voided checks, government-issued IDs, or articles of incorporation — as part of merchant onboarding, configured per connection.

• Enforced in the boarding form. Required document sections are clearly marked, and merchants can't move past a step until every required document is uploaded.
• Counts toward readiness. Outstanding required documents now count as missing requirements, so a merchant isn't marked Ready until all required documents are provided.
• Available over the API. The GET /v1/requirements/supportedParameters/{connectionId} response now reports which document types are supported and required per connection, so your integration can present and enforce them programmatically.

Improvements

Connections & Merchant API

• Phone numbers standardized to E164. Contact and signing-contact phone fields now validate and store in canonical E164 format (+15551234567). Boarding forms still display numbers in the familiar (555) 123-4567 format and convert what you type automatically, and the merchant API now returns phones in E164 on read for symmetry with writes. Existing phone records were migrated automatically — no action required.

Boarding Form

• Consistent multi-entity steps. The Banking step's account tab bar now matches the Owners step — same visual style, sticky behavior, and "Add" button placement.
• Greensky partner channel. Greensky boarding now correctly sources the partner channel from the processor MID.
• Polish. Added spacing around the Add Owner button on the Owners step.

Dashboard

• Plans page refreshed. The Plans page has been updated to our new design system for a cleaner, more consistent look.
• Quick Actions moved to the header. Quick Actions now lives in the header so it's always visible, regardless of platform or sidebar state. The Ctrl+K / ⌘K shortcut still works everywhere.

Integrations

• Consistent TPT expiration format. Third-party tokenization (TPT) result files now use a consistent MMYY card-expiration format across all processors.

Bug Fixes

Boarding Form

• New owner tabs no longer show an error count before you've entered anything. Validation feedback now waits until you've interacted with the new owner.
• "Same as Business Address" now works. On the Business Location step, the checkbox correctly copies and saves the mailing address and remembers its state when the form is reloaded.
• Greensky Business Category now pre-populates correctly on page load. (Fixed two related root causes affecting both single- and multi-connection forms.)
• Save feedback on Contacts steps. The Ramp and Greensky Contacts steps now show a loading state while saving, like every other step.
• Consistent Contacts headers. The Ramp Contacts step header now matches the styling used across the other Contacts steps.

Connections & Merchant API

• First-time Rainforest connections work again. The Preczn Webhook URL now populates on the Connections page, so a first-time Rainforest connection can be completed.
• Ramp requirement templates are editable again. Removed stale mandatory billing-name entries that were causing every Ramp template edit to fail.
• Ramp applicant contact requirement restored. The applicant role now appears in supportedParameters, in the merchant API response, and in the API reference.
• Ramp connections no longer go Active prematurely. A new merchant with a Ramp connection is no longer marked Active before credentials are entered and boarding is complete.
• Partial requirement-template updates. PATCH /v1/requirements/{requirementsTemplateId} now accepts partial updates without requiring the name field.

Dashboard

• Dark mode menu hover restored. Dropdown and context-menu items show visible hover highlights again in dark mode.

API Documentation

• "Update a contact" request body documented. The endpoint now shows a complete request body schema and example in the API reference. (Runtime behavior was never affected.)