Changelog
Back to All

7/16/2026 Release

5 days ago by Clay Hefner

This release focuses on the merchant boarding experience: a redesigned document-upload flow with built-in KYC/KYB guidance — including document requirements, common issues, and visual examples — plus multi-connection boarding forms, a customizable welcome section, in-line contact editing, and expanded Greensky support — plus a set of validation and usability fixes.

Jump to: New Features · Improvements · Bug Fixes

New Features

Built-in KYC/KYB document guidance on the boarding form

The boarding form now walks merchants through every required document — what to provide, why submissions get rejected, and what a good one looks like — so they can get it right without back-and-forth.

  • Guidance for every document type. On the boarding form, each required document now comes with tailored KYC/KYB guidance — what the document is, exactly what it needs to show, and the acceptance criteria — surfaced right where merchants upload.
  • Common issues called out up front. Guidance highlights the most common reasons a document gets rejected, so merchants can get it right the first time and avoid back-and-forth.
  • Visual SVG examples. Clear, illustrated SVG examples show merchants what a good submission looks like for each document.
  • Guidance modal before the dropzone. A single Upload entry point opens a modal that presents the requirements, common issues, and examples first — then the dropzone.
  • Redesigned upload control. A single, equal-footprint upload component replaces the old per-field controls — with a filename pill, multi-file support, an in-progress state, and full keyboard/screen-reader accessibility.
  • Consistent uploads across every step. Supporting Documents, per-owner attachments (front/back ID and utility bill), and per-account banking documents all use the same guided, multi-file component.
  • Required-document alerting. Missing required documents now show a persistent inline error and a clickable badge, plus a toast on save, so nothing is missed before submission.

Create multi-connection boarding forms in the dashboard

You can now board a merchant to several connections from a single form. Form creation moves into a redesigned side drawer with a status-aware connection picker and template-driven settings.

  • Create forms in a side drawer. Creating a boarding form now happens in a right-side drawer instead of a modal, giving more room for configuration.
  • Select multiple connections at once. A grouped, status-aware checklist lets you scope a single boarding form to multiple connections in one step.
  • Template-inherited form settings. An accordion surfaces overrides for form type, expiration, auto-transmit, and terms & conditions — pre-filled from the selected template.
  • In-drawer success state. On submit, the drawer shows a success view with a one-click link copy, a security note, and a summary of the form's settings.
  • Graceful edge cases. Zero-connection, all-disabled, and Test-vs-Live scenarios are all handled cleanly.

Customizable welcome section for boarding forms

Boarding forms can now open with a configurable welcome step — your introduction, agreement content, and the details of the person completing the application.

  • Configure a Welcome step. Template editors can now define a custom welcome section — an introduction, agreement content, and the "person completing the application" fields.
  • Rendered for the applicant. The Welcome / Person Completing step renders at the start of the form, and submitted values are persisted with the form.
  • Greensky prefill. The Greensky "Person Completing Application" now prefills from the values saved on the form.

Edit contact details in the boarding form

You can now edit a contact directly from the boarding-form contact pickers — no need to leave the form to correct a detail — backed by a new form-scoped contact update endpoint.

Greensky enhancements

Greensky connections gain more flexible setup, including support for a Sponsor ID and an optional platform API key.

  • Sponsor ID support. An optional Sponsor ID can be set on the Greensky connection in the dashboard; it is persisted and transmitted with the application.
  • Optional platform API key. The Greensky platform API key is now optional at connection setup.

Improvements

Boarding form

  • Unsaved-changes guard. The Business Information step now warns before you navigate back with unsaved changes.
  • Clearer Adyen T&C message. The "already accepted" message on the Adyen for Platforms terms step has been improved.
  • Centered content on large screens. Boarding-form step content is now constrained and centered on wide displays for better readability.
  • Ramp policy agreement. The Ramp Contacts step now displays the Ramp policy agreement.
  • Greensky minimum-volume validation. The boarding form now enforces Greensky's $1,000 minimum for annual sales volume, instead of allowing values below the API minimum.

Miscellaneous

  • Readable missing-data output. missingRequiredData is now sorted by entity scope for deterministic, easy-to-scan output.
  • Standardized contact timestamps. The Merchant API now returns contact timestamps as createdOn / modifiedOn in ISO-8601, matching platform convention.
  • Cleaner account-closure state. Closing a merchant account at a connection now clears the associated actionRequired / actionDescription.
  • Google Pay button styling. Google Pay initialization now accepts optional button-styling arguments.

Bug Fixes

Boarding form

  • Save & Go Back error feedback. "Save & Go Back" no longer fails silently on invalid data — validation errors are now surfaced in the UI.
  • New contacts available across connections. A contact created during a multi-connection boarding form is now available in later connections' contact steps.
  • No more empty Greensky contacts flash. The Greensky Contacts step no longer flashes an empty "Pick or add a contact" state each time you enter it.

Dashboard

  • Mandatory badge preserved. The requirements template editor no longer drops the Mandatory badge for backend-mandated fields when editing an existing template.
📘

Questions about this release? Reach out to your Preczn contact or our support team.