PROD Release Notes – Outbound Payments (AN_OUTPAY_V8)

Makes Vendor Phone Number Optional

What’s New

The phone number field is now optional when creating or updating a vendor. This change applies consistently across both the user interface and backend APIs. Existing validation rules have been updated to allow vendor records without a phone number.

Why It Matters

You can now create and manage vendor records without requiring a phone number. This simplifies onboarding for vendors where contact numbers are unavailable or unnecessary, reducing friction in data entry.

Changes

• Parameter: phoneNumber
• Change Type: Modified (now optional)
• Affects: Vendor create and update endpoints

Allows Cancellation Of Checks In Print Queued Status

What’s New

Checks that are in a “Print Queued” state can now be canceled before they are printed. This introduces additional control over the check processing lifecycle and prevents unwanted check issuance.

Why It Matters

You can now stop checks before they are printed, reducing errors and avoiding the need for manual reversals or corrections after printing.

Omits Duplicate DBA Name On Printed Checks

What’s New

When the Merchant DBA (Doing Business As) name matches the Merchant name, the system no longer prints the DBA name on checks. This removes redundant information from printed output.

Why It Matters

You get cleaner, more readable checks without duplicate business names. This improves the presentation and avoids confusion for recipients.

Excludes Bundle Address For USPS First Class Shipping

What’s New

The system no longer includes the bundle address when USPS First Class is selected as the shipping method. This avoids requiring unnecessary fields such as phone numbers for this shipping type.

Why It Matters

You can process shipments with fewer required fields when using USPS First Class. This streamlines the workflow and reduces validation errors tied to unnecessary address data.

Suppresses Transit Status After Delivered Webhook

What’s New

If a “Delivered” webhook is received, the system stops sending or displaying subsequent “In Transit” status updates. This ensures that delivery status is not overwritten by outdated tracking events.

Why It Matters

You now see accurate and consistent delivery statuses. This prevents confusion caused by conflicting tracking updates after a package has already been marked as delivered.

Implements Secure Webhook Validation For Checkeeper

What’s New

Incoming webhooks from Checkeeper are now validated using a signature-based verification process. This ensures that only trusted webhook events are accepted by the system.

Why It Matters

You can trust that webhook events are authentic and have not been tampered with. This improves the security of your payment workflows and reduces the risk of processing malicious or invalid requests.

Release Date: Feb 26, 2026

Release Status: Deployed to PROD

This release bundle contains Outbound payments API’s

Features Deployed to UAT

Merchant Portal Enhancements

Vendor Management:

Phone number made optional in Add/Edit Vendor, implemented across UI and Backend (Secure & Open APIs)

Client Facing Impact: Yes

Check Printing and Formatting:

Allow Cancellation of Checks in Print Queued Status
Merchants can now cancel Checks that are still in Print Queued status

Do Not print Merchant DBA Name when same as Merchant Name
If Merchant DBA name matches Merchant Name, the DBA name is omittedon the printed check to avoid redundancy.

Client Facing Impact: Yes

Exclude Bundle Address for USPS First Class Shipping Methods

Bundle address is now excluded when USPS first class shipping method is selected [only shipping method for now], to avoid phone number being mandate

Client Facing Impact: Yes

Omit Transit Status if Delivered webhook is received prior

Transit status updates are now omitted when a delivered webhook is already received, preventing wrong display of status

Client Facing Impact: Yes

Secure Webhook Validation for Checkeeper

Added Signature-based webhook validation to securely verify incoming Checkeeper webhook requests

Client Facing Impact: Yes