Customer Portal Changelog
2026.10.29.1
Section titled “2026.10.29.1”What’s new:
Section titled “What’s new:”Account Intelligence comes to the portal: a team set up for it can upload a CSV of bank accounts, have each row scored in the background and download the results. Transaction and payout details now link to each other, clawback types are shown as readable labels with payor details where they apply, and changes to users and access ask for confirmation and are recorded.
Why it matters:
Section titled “Why it matters:”Accounts can be scored in bulk from a file, and the results come back in the same layout with a score and decisioning insights on every row. A transaction and its payout can be followed from either record, and a vendor’s administrators can see that every access change is confirmed before it is saved and leaves a record of who changed what.
Highlights:
Section titled “Highlights:”- An Account Intelligence section with Upload and Downloads pages appears for a team whose Account Intelligence credentials GrailPay has set up. Vendor admins and vendor users can upload and download for their own team, Vendor User (read-only) can download, and a dedicated account-intelligence role can use these two pages and nothing else
- Upload offers a CSV template (
external_id,account_number,routing_number, name, organization,ssn,ein, phone, email and address columns) and two toggles, Name match and Taxpayer ID match. A file is accepted up to 10 MB and 5,000 rows, with one batch in flight per team - A file that is not a CSV, lacks the
account_numberorrouting_numberheader, is empty or is over the limits is explained on the Upload page and processes no rows. Within an accepted file, an invalid row is marked and does not stop the rest - The uploader is notified when processing starts and when the results file is ready. Downloads lists the team’s batches with filename, uploader, the two toggles, status, row counts and timestamps, and offers the results file once it is written
- The results file repeats the submitted columns and adds
status,error,confidence_score,request_idand the decisioning-insight columns. A row that was invalid or hit a service error carries an error and no score - Transaction details shows a Payout tab when the transaction has a payout, with the payout’s summary, payee account, ACH details and return code and a link to the payout; vendor admins can reveal the payee’s bank account there. Payout details shows a Transactions tab with each transaction’s UUID, amount, status and a link, numbered when there is more than one
- Clawback types appear as labels such as Reverse Payout and Vendor Fee on the list and the detail page, and clawback details adds a Payor Details section beside Payee Details: payee details are filled for transaction and vendor-fee clawbacks, payor details for reverse-payout and refund clawbacks
- Creating a user, changing a user’s role or status, changing merchant access and permanently deleting a user ask for confirmation first, and each change is recorded with who made it, the values before and after, and when
2026.10.19.1
Section titled “2026.10.19.1”What’s new:
Section titled “What’s new:”The transaction timeline now continues past capture. Payout, clawback and refund events appear as their own stages, so a transaction can be followed from capture to the money leaving.
Why it matters:
Section titled “Why it matters:”A transaction that has reached payout, been clawed back or been refunded shows the whole story on one Timeline tab, with the return code on a failed leg, instead of ending at the last capture event.
Highlights:
Section titled “Highlights:”- The Timeline tab adds a Payout stage with the payout’s started, created, processed, sent, settled, failed and canceled events in time order after capture, and the progress tracker shows Capture then Payout once a payout event exists
- A Clawback stage lists the clawback’s start and its ACH events, and a Refund stage lists the refund’s start, capture leg and payout leg; a second refund is numbered in the order it was created
- Progress runs Capture, Payout, Clawback, then Refund. A transaction still in capture shows no empty later stage, and the capture timeline stays in place if a related record cannot be loaded
- The transaction status filter no longer offers CAPTURE COMPLETE; a transaction that carries that status still shows the label
2026.10.14.1
Section titled “2026.10.14.1”What’s new:
Section titled “What’s new:”Transactions, payouts, refunds and clawbacks can be exported to CSV from their list pages and from a merchant’s tabs. The export runs in the background and the file is collected from a new Data Exports page. Timestamp column headers now carry (ET) instead of repeating the zone on each value.
Why it matters:
Section titled “Why it matters:”Filtered activity can be taken out of the portal for reconciliation or analysis with a stable column layout, and a large export does not hold up the browser while it runs.
Highlights:
Section titled “Highlights:”- Export CSV on the Transactions, Payouts, Refunds and Clawbacks pages and on the matching tabs of Merchant Details exports the rows that match the current filters. At least one filter is required, an invalid filter value or an empty result keeps the button disabled, and merchant users export only their own merchant’s records
- The export runs in the background. A notification confirms it started, and the file appears on Data Exports under Operations with its type, status, record count and timestamps and a Download action
- Transaction columns: UUID, Client Reference ID, Created At (ET), Amount, Status, Payor Merchant Name, Payee Merchant Name, Bank Identifier, Modality, ACH Created At (ET), ACH Settled At (ET), ACH Failed At (ET), Return Code, Payor User UUID and Payee User UUID
- Payout, refund and clawback exports follow the same layout with Payor Name and Payee Name for any party. Payouts add Type, refunds carry the capture leg and the payout leg separately, refunds and clawbacks include the Transaction UUID, and clawbacks have no Modality column
- Dates in an export use the on-screen format
- Every timestamp column header on screen ends in (ET), such as Created At (ET), and the EST or EDT suffix is dropped from each value
- When GrailPay creates a user on a team it can set a password directly; leaving it blank still emails the user a link to set their own
2026.10.8.2
Section titled “2026.10.8.2”What’s new:
Section titled “What’s new:”Every timestamp in the portal is shown in Eastern time, with EST or EDT after the value, and the Billing Items and Billing Summary pages read the Payments API’s entity-based billing responses.
Why it matters:
Section titled “Why it matters:”Times on transactions, payouts, people, merchants, users and teams can be compared directly, whichever page they appear on. The billing pages now show the billed entity rather than assuming a merchant.
Highlights:
Section titled “Highlights:”- Displayed timestamps use Eastern time and end with
ESTorEDTfor that instant. Stored values, API payloads and date filters are unchanged - Billing Items shows Entity, Entity UUID and Client Reference ID columns in place of Merchant and Merchant UUID, and its Merchant Name and Merchant UUID filters are replaced by an Entity UUID filter
- Billing Summary’s Merchant UUID filter is now Entity UUID; its Merchant Name filter stays
2026.9.30.1
Section titled “2026.9.30.1”What’s new:
Section titled “What’s new:”User management now lives on the team’s page, three read-only roles join the existing roles, and the Teams area is limited to vendor admins and vendor users.
Why it matters:
Section titled “Why it matters:”A vendor can give someone view-only access to the portal without also giving them the ability to move money or change records, and sees its users in the context of their team, so ownership and access are clear. A merchant team sees only its own merchant’s activity.
Highlights:
Section titled “Highlights:”- Vendor admins and vendor users can open Teams and see their own team and the teams under it; processor and merchant roles do not see Teams, and creating a team is done by GrailPay
- Vendor admins can invite a user onto their own team or a team under it from the team page; the invitation sends the password-setup email
- New roles: Processor User (read-only), Vendor User (read-only) and Merchant User (read-only). Each sees the same pages as the matching User role and cannot create a transaction, cancel, refund, or add or edit a merchant, person or business; Vendor User (read-only) keeps Billing
- A merchant team is linked to one merchant, and its users see only that merchant’s transactions, payouts, refunds, clawbacks and returns
- The GrailPay API user is set on the team and inherited by its users, so the API User ID on a processor, vendor or merchant user’s form is shown read-only
2026.9.24.1
Section titled “2026.9.24.1”What’s new:
Section titled “What’s new:”The Transactions tab on Merchant Details uses the same table as the Transactions page, and Speed, Bank ID and Trace ID are shown on the transaction list and on transaction details.
Why it matters:
Section titled “Why it matters:”A merchant’s transactions are reviewed with the same columns, status badges, filters and Review action as the main list, and a transaction’s two bank identifiers are labeled the same way wherever they appear.
Highlights:
Section titled “Highlights:”- Merchant Details → Transactions lists only that merchant, with the Date Created, Status, Details, ACH Details, Amount and Review columns; the Merchant UUID filter stays on the Transactions page
- Speed shows Standard ACH or Fast ACH on the list and on transaction details
- Transaction details shows Bank ID and Trace ID as two lines in place of the single Bank Identifier line; both lines always appear, an empty value shows as —, and Copy is offered only when there is a value
- The list filter for the ACH capture identifier is labeled Trace ID
- SEC Code can still show as — when the API does not return it
2026.9.18.1
Section titled “2026.9.18.1”What’s new:
Section titled “What’s new:”The transaction list, transaction details and Create Transaction pages have been rebuilt. Creating a transaction now ends with a confirmation step, and a person, business or merchant can be found or added from the form.
Why it matters:
Section titled “Why it matters:”The list shows each transaction’s ACH detail at a glance, the details page shows the request that created a transaction and the webhooks sent for it, and the confirmation step gives a second look at the parties and the amount before a transaction is created.
Highlights:
Section titled “Highlights:”- Transaction list: six columns, Date Created, Status, Details, ACH Details, Amount and Review. Details shows Client, Speed, SEC Code, Payout Delay, Bank ID and Trace ID; ACH Details shows the ACH status with the timestamps and return code that are present; a missing value shows as —
- Dates are shown in Eastern time as
m/d/Y @g:ia, for example08/16/2026 @12:29pm; filters, summary totals, CSV export and Create Transaction are unchanged - Transaction details: Details, Timeline, Webhooks and Creation Request tabs, with the open tab kept in the URL. Creation Request shows the API request that created the transaction and its response; Webhooks lists the deliveries sent for it; empty fields are hidden rather than shown blank
- Vendor admins can reveal the payer’s account and routing numbers on transaction details for a manually entered bank account; each reveal is recorded, and other roles see the numbers masked
- Create Transaction: the amount is entered in dollars, with two decimals and comma separators, and sent to the API in cents
- Save opens a Confirm Transaction step showing Payer, Payee, Amount and Speed; each party is looked up by UUID and shown by name, an unknown UUID or an incomplete name shows a warning, and at least one party must be a merchant
- Find or add a person, business or merchant from the form; Add Business and Add Merchant are multi-step wizards with a Review step, and vendor admins can add merchants
- The Source and Destination account fields are removed (the payer and payee determine the accounts), Billing Processor MID is removed from Add Person and Add Business, and labels say Payer rather than Payor
2026.9.11.1
Section titled “2026.9.11.1”What’s new:
Section titled “What’s new:”Bank account and routing numbers are masked everywhere in the portal, with a reveal action for vendor admins that is recorded each time it is used. Merchant and person pages now list the record’s bank accounts, Merchant Details gains Compliance, Beneficial Owners and Bank Accounts tabs, and the Merchants and People tables have been reorganized.
Why it matters:
Section titled “Why it matters:”Bank details are visible only through a deliberate, permitted action, and every reveal leaves a record of who revealed which account and when. The Merchants list can be assessed at a glance, and the Compliance tab shows which check is responsible when a merchant is not clear.
Highlights:
Section titled “Highlights:”- Account and routing numbers are masked in tables, detail views and forms. Vendor admins can reveal a number with the Reveal action; each reveal is recorded with the user, the record it was revealed on and the time
- Merchant Details has Compliance, Beneficial Owners and Bank Accounts tabs. Compliance breaks the merchant’s compliance status into the business verification and each beneficial owner’s identity verification
- Merchant Details and Person Details list the record’s bank accounts, masked by default
- Merchants table columns are now Name, Compliance Status, Activation Status, Tax ID, Created At and UUID. Compliance Status replaces the previous verification column and rolls up the merchant’s full compliance picture
- People table columns are now First Name, Last Name, Email, Phone, Status, Created At and UUID, with filters for first name, last name, client reference ID and person UUID
2026.8.3.1
Section titled “2026.8.3.1”What’s new:
Section titled “What’s new:”Invitation and password-reset links now stay valid for 7 days.
Why it matters:
Section titled “Why it matters:”Previously a link expired after 8 hours, so a new user who did not open the invitation the same day had to be invited again. A week leaves time to complete setup on the first invitation.
Highlights:
Section titled “Highlights:”- Applies to the invitation email sent when a user is added and to password-reset emails
- A link expires 7 days after the email is sent
2026.7.13.1
Section titled “2026.7.13.1”What’s new:
Section titled “What’s new:”A new Returns page under Money Movement lists every ACH return visible to your account, whichever leg of the transaction it occurred on.
Why it matters:
Section titled “Why it matters:”Returns on the debit leg and on the payout leg are in one list with their reason codes, so returned transactions and their status can be monitored from one place.
Highlights:
Section titled “Highlights:”- Columns: Leg (Capture or Payout), Amount, Returned At, Return Reason, and the UUIDs of the related transaction, payout, clawback and reverse payout
- Filters: leg, R-code, start and end date, amount, bank ID, and transaction, payout, clawback, reverse payout and entity UUID
- Rows sort by amount and by the returned-at date, with pagination
2026.3.26.1
Section titled “2026.3.26.1”What’s new:
Section titled “What’s new:”This release includes routine dependency updates across the platform and introduces password reset functionality with SendGrid email delivery for the Customer Portal.
Why it matters:
Section titled “Why it matters:”Keeping dependencies up to date ensures the platform remains secure, stable, and compatible with the latest improvements from upstream libraries. The addition of password reset support with a reliable email delivery provider improves the admin experience and account security.
Highlights:
Section titled “Highlights:”- Updated over 30 packages across the platform, including Laravel, Symfony, Livewire, and security-related libraries
- Added password reset functionality for the Customer Portal with SendGrid as the mail driver
- Fixed an issue where admin password resets failed due to an undefined route
2025.10.7
Section titled “2025.10.7”Release Features
Section titled “Release Features”- Updated consumer integration to support the new v3 onboarding response format for Person and Business, ensuring consistent data handling and UI display.
2025.10.6
Section titled “2025.10.6”Release Feature
Section titled “Release Feature”- V3 API Response Standardization: All V3 APIs of List and Showing (Person, Business, and Merchant) now follow a unified response contract with consistent structure. Error responses are now standardized across all endpoints, providing clearer, more consumer-friendly messages with proper attribute naming in validation errors.
- Enhanced Relational Data: We’ve introduced a new relations object across all V3 endpoints, making it easier to understand entity relationships:
- Person responses now include related Business or Merchant UUIDs.
- Business and Merchant responses include associated Person UUIDs.
Maintenance Items
Section titled “Maintenance Items”Billing Improvements: Fixed filter inconsistencies in Billing Item and Summary endpoints, ensuring accurate and reliable query results across both endpoints with consistent behavior.
Maintained by EkLine

