Paystand Platform Release Notes – Paystand Help Center

Release 25.40.2 – October 1st, 2025

Fixed a bug causing 404 errors on Magento checkout pages. Root cause was traced to expired or invalid access tokens, which are now properly handled.

Replaced the per-message Kafka producer pattern with a singleton producer architecture. This significantly improves performance, reduces resource usage, and adds retry logic, health monitoring, and batch/transactional messaging support.

Release 25.39.4 – September 25, 2025

Previously, bank and teampay payments were blocked from sending emails or triggering downstream actions until the Assurety certification process completed—resulting in delays. These actions now trigger immediately at the same step as card payments.

Addressed a security concern where expired sessions would leave sensitive content visible in the UI, despite navigation controls being disabled.

Release 25.39.2 – September 22, 2025

Resolved a billing issue where a B2B bank network payment was incorrectly charged a fee, despite the merchant’s F&I plan not including one. The root cause has been addressed to prevent similar fee misapplications in the future.

Introduced a globally unique identifier (GUID) for all incoming requests across payment flows. This enables easier debugging and traceability across system logs.

Release 25.38.4 – September 18, 2025

Merchants can now embed Checkout V5 on their websites to collect payment details, tokenize them, and link them to Customer Records—without relying on webhooks. This enables use cases like trial-period billing where autopay is triggered after onboarding.

Fixed a bug in Checkout V5 where selecting one bank would sometimes display a different bank in the authentication screen. The flow now reflects the correct selected bank consistently.

Release 25.38.2 – September 16, 2025

The WooCommerce “Learn More” link in Dashboard > Integrations has been removed after it was found to point to a deprecated page. It’s now replaced with a new CTA labeled “Request WooCommerce Extension”, which opens a pre-filled email to solutions@paystand.com allowing merchants to request the extension directly. This prevents confusion and improves support for WooCommerce onboarding.

Release 25.37.4 – September 11th, 2025

Resolved a critical issue where the Paystand Checkout modal failed to display when accessing Magento via multiple store views. The fix ensures modal windows now load correctly and display payment forms across all views.

Release 25.37.2 – September 9th, 2025

Enabled embedded Checkout V5 flows for tokenization and autopay setup without requiringexternal webhooks. Payers can now enter their payment method directly on merchant websites, trigger token generation, and have the token linked to a Customer Record for future autopay charges after a trial period. This supports seamless Save Now → Charge Later flows

Release 25.37.1 – September 8th, 2025

Updated taxPercentage logic for Level 2/3 Visa transactions to use the payer’s location, not the merchant’s, in preparation for Visa’s policy change. This ensures continued eligibility for L2 discounts by aligning with updated tax reporting requirements.

Release 25.36.4 – September 4th, 2025

Added internal support for Stripe’s Multi-Currency Settlement feature, enabling test onboarding of UK-based merchants settling in USD. This prepares the system for private preview rollout by validating API behavior, FX settlement logic, and regional constraints.

Introduced configuration to pass Stripe’s MCS fee (e.g., 1%) through blended pricing. Dashboard reflects unified card fee rate, and backend logic ensures accurate fee attribution in both reporting and settlements.

Checkout now detects whether a user is logged in. Logged-in users see pre-filled billing info and access saved payment methods, while guest users follow the traditional flow. Enhancements include saved method toggles and improved UI navigation between flows.

Resolved two key issues in the Lockbox overpayment filter: Fixed pagination bug where overpayments were only searched on the current page. Filter logic now applies only after clicking ‘Apply Filter,’ preventing accidental filtering on page change.

Release 25.31.4 – July 31st, 2025

Fixed an issue where certain banks (e.g., First Hawaiian Bank) triggered an Invalid US Bank Account Number error during login, blocking payers from completing payments.

Addressed an Angular digest cycle issue that caused the Receivables navigation link in the sidebar to not load consistently. Navigation now works reliably across all customers.

Added fallback handling when banking partner returns a DEGRADED status. Payers can now complete payments by manually entering ACH details, with tracking for how often this occurs.

Resolved inconsistent ordering logic that caused scheduled payments (e.g., Feb, May, Jul) to be missing from the payer history. Payments now appear in the correct order without gaps.

Release 25.31.1 – July 29, 2025

Merchants can now filter checks in the Lockbox by overpayment type: all checks, only overpayments, or exclude overpayments. This makes it easier to track and manage overapplied checks within the matching workflow.

Updated the overpayment messaging when matching checks to clarify that unmatched amounts are recorded as unapplied payments, not credit memos. This correction improves clarity and reduces merchant confusion during check application.

Added a new setting that sends checks to the Unmatched queue when not all referenced invoices are identified. This prevents false overpayments and allows for cleaner manual

Release 25.30.4 – July 24, 2025

Improved error handling and UI validation for ACH bank login. Unsupported account types (non-Checking/Savings) are now clearly labeled as “Invalid Account Type” instead of failing silently. Fix enhances visibility and reliability for Canadian merchants.

Resolved a rare race condition that prevented certain push payment transactions from appearing in the Dashboard. Added retry logic and improved transaction syncing, ensuring all deposits are consistently reflected.

Added support for blind carbon copy (BCC) recipients in payment notification emails via custom templates. Now, secondary contacts listed in the merchant’s UI will receive payment alerts as expected.

Release 25.30.2 – July 22, 2025

Updated dashboard behavior to display “eCheck XXXX” as the payment method for Smart Check transactions, improving merchant visibility and reconciliation. Check number support will follow in a future update.

Release 25.29.4 – July 17, 2025

Resolved a conflict where custom fields added via the Dashboard disrupted Single Invoice Checkout UI, allowing users to skip inputs or causing the Continue button to be disabled in Virtual Terminal. Both flows now behave as expected.

Corrected a bug where CAD merchants using Checkout V4 encountered errors when clicking bank logos. The update adds logic for dynamic bank ID resolution and restores expected behavior for bank selection.

Release 25.29.2 – July 15, 2025

Enhanced error-handling logic to correctly capture and display failed payment reasons for transactions processed, improving visibility into unsuccessful transactions.

Improved matching logic for checks processed through the Smart Check workflow. The update ensures a single failed invoice no longer blocks the matching of valid ones in the batch.

Resolved an issue where the embedded Paystand checkout modal failed to display properly in certain Magento environments. This improves checkout stability for merchants using Paystand inside ecommerce flows.

Updated logging for bank login events to align with newer standards and support better debugging and diagnostics.