Product update: July 2026
July’s release adds corporate cards, ACH payouts, SEPA accounts and clearer sanctions exposure, alongside safer cancellations, new asset support and stronger exports.
The July 2026 update adds corporate cards, ACH payouts and SEPA accounts for sending and receiving euros, including SEPA Instant. It also makes sanctions exposure easier to investigate, records why payment intents were cancelled and improves dust recognition. Finance teams gain support for additional assets, clearer counterparty history, improved invoices, more ledger filters and PDF, CSV or XLS exports.

The July 2026 Stablerail update expands how finance teams can spend and move company funds while improving transaction review and audit evidence. The main additions are corporate cards, live ACH payouts and SEPA accounts for euro transfers, including SEPA Instant. The release also provides more detail on sanctions exposure, safer cancellation controls, better counterparty context and more flexible finance exports.
What changed in July 2026
The table separates features that are available now from rails that remain in progress. Finance teams should treat “in progress” as a roadmap status rather than build a funding or payment process around an assumed launch date.
| Update | Status | What changed | Finance and control impact |
|---|---|---|---|
| Corporate cards | Live | Companies can issue and manage corporate cards inside the platform. | Adds a card-based spending route that should be incorporated into approval, reconciliation and close procedures. |
| ACH payouts | Live | ACH can now be used for payouts. | Provides a bank payout option alongside digital-asset transfers. Teams should document settlement and exception handling before moving recurring payments. |
| SEPA accounts | Live | Euro transfers can be sent and received, including through SEPA Instant. | Supports EUR collections and payments. Treasury should confirm the appropriate route for each beneficiary and payment deadline. |
| GBP and SWIFT rails | In progress | Additional sterling and international bank-transfer rails are being developed. | Do not treat these rails as available when planning liquidity, vendor payments or account migrations. |
| Sanctions exposure | Live | The risk dossier now breaks exposure down by category instead of presenting only one aggregate number. | Reviewers can investigate the source of exposure, including links to mixers, exchanges and iGaming categories. |
| Cancelled intents | Live | Cancellation reasons are visible, cancellation requires double confirmation and the event enters the audit trail. | Reduces accidental cancellation risk and gives reviewers evidence of what happened. |
| Dust recognition | Improved | The system is better at identifying very small “dust” transactions. | Helps teams distinguish immaterial or suspicious small transfers from ordinary treasury activity. |
| Additional assets | Live | Support was added for Bitcoin, Litecoin, Bitcoin Cash and Ripple/XRP. | Asset support expands, but each asset should still be governed by the company’s approved treasury policy. |
| Finance operations | Improved | Invoices, counterparty reminders, exports and ledger filters were updated. | Makes review, reconciliation and evidence collection more practical for finance teams. |
Corporate cards add a new company spending route
Corporate cards can now be issued and managed within the platform. For a finance team, the important change is not simply card availability: card transactions become another flow that must be assigned an owner, reviewed and reconciled with the general ledger.
Before issuing cards, controllers should define who may request one, who approves issuance, which expense categories are permitted and how supporting documents are collected. They should also document the card’s funding and settlement process rather than assume it behaves like an ACH, SEPA or onchain payment.
A new payment method should not create a new control standard. Card spending, bank payouts and stablecoin transfers should ultimately produce consistent approvals, accounting records and audit evidence.
ACH and SEPA expand bank payment options
ACH payouts are now live. This gives treasury teams another way to pay bank-account beneficiaries without requiring the recipient to accept USDC, USDT or another digital asset. Before moving an existing payout process, confirm beneficiary details, expected settlement timing, return handling and the internal owner responsible for investigating exceptions.
SEPA accounts are also live for sending and receiving euro transfers, including SEPA Instant. This can support EUR collections and supplier payments while keeping the transfer within familiar bank rails. Treasury teams should still select the route based on beneficiary eligibility, urgency and their own liquidity position rather than assuming every euro transfer should be instant.
GBP and SWIFT rails remain in progress. Because no launch date is stated in this update, they should not yet be included as available routes in treasury forecasts, payment instructions or business continuity plans.
Sanctions exposure is now easier to investigate
The risk dossier previously presented sanctions exposure as a single figure. It now shows a breakdown of the underlying exposure by categories such as mixers, exchanges, iGaming and similar activity. That gives reviewers more context when deciding whether an address or transaction requires escalation.
A category is not, by itself, a legal conclusion or proof that a counterparty is sanctioned. The breakdown should be considered alongside sanctions and address screening before a transfer is sent, the counterparty’s identity, the transaction’s purpose and the company’s risk procedures.
Finance and compliance teams should agree on who reviews the dossier, what requires escalation and what evidence must be retained. They should also understand the methodology behind any percentage before using it as a formal threshold or reporting it outside the business.
Cancelled payment intents now leave clearer evidence
Users can now see why an intent was cancelled. The cancellation flow requires a double confirmation, helping to prevent a misclick from stopping an intended payment. The cancellation event is also written to the audit trail.
Together, these changes answer three questions that frequently arise during payment review: what was cancelled, why it was cancelled and whether the action was deliberate. They complement approval and signing-quorum controls but do not replace a documented process for re-creating or re-approving a cancelled payment.
Smaller operational improvements
Better recognition of dust transactions
Dust transfers are tiny blockchain transactions that may be economically immaterial and can also be associated with spam or address-poisoning attempts. Recognition has been improved so these transfers are easier to identify. Reviewers should still verify addresses independently and avoid copying a destination from transaction history solely because it looks familiar.
Support for more assets
The platform now supports Bitcoin, Litecoin, Bitcoin Cash and Ripple/XRP. Technical support does not automatically make an asset appropriate for corporate treasury use. Each asset should pass the company’s approval, accounting, custody, liquidity and risk review before funds are held or transferred.
Invoices and counterparty reminders
Invoice screens and emails have been improved, with wallets displayed more clearly. When paying a previously used counterparty, the payment flow now shows recent transactions with that counterparty, including the token and blockchain used. This context can help identify an unexpected change, but prior history should not be treated as independent verification of current instructions.
Exports and ledger filters
Ledger and banking transactions can now be saved as PDF, CSV or XLS files, and ledger filters offer more customisation. PDF can provide a stable review artifact, while CSV and XLS files are better suited to reconciliation and analysis. Teams should retain the export parameters, reporting period and reviewer sign-off so the files remain meaningful audit evidence.
Finance-team rollout checklist
- Update the payment-method register: add cards, ACH and SEPA, with an owner and approved use case for each.
- Separate live features from roadmap items: keep GBP and SWIFT out of production procedures until they are available.
- Define card controls: document issuance approval, permitted spending and reconciliation responsibilities.
- Test bank workflows: run controlled ACH and SEPA payments before moving material or time-sensitive transactions.
- Set escalation rules: define how sanctions-exposure categories and dust transactions are investigated.
- Review counterparties independently: use prior token and blockchain history as context, not as proof that new instructions are valid.
- Standardise evidence: choose PDF, CSV or XLS exports based on the review, reconciliation and retention requirement.
What the release means for treasury operations
July’s update connects more day-to-day finance activity in one corporate treasury workflow: card spending, US bank payouts, euro transfers, stablecoin operations and exportable records. The control improvements are equally important. More detailed risk information, deliberate cancellation steps and clearer transaction context help finance teams review activity without relying on a single risk score or an unexplained status change.
Frequently asked questions
What did the July 2026 product update add?
The update added corporate cards, ACH payouts and SEPA accounts for sending and receiving euros, including SEPA Instant. It also improved sanctions-exposure analysis, cancellation records, dust recognition, invoices, counterparty reminders, exports and ledger filters.
Does Stablerail support ACH and SEPA transfers?
ACH payouts and SEPA accounts are live as of the July 2026 update. SEPA accounts support sending and receiving euro transfers, including SEPA Instant.
Are GBP and SWIFT payments available?
No. The July 2026 update lists GBP and SWIFT rails as in progress, so finance teams should not treat them as available or assume a launch date.
What does the sanctions-exposure breakdown show?
The risk dossier breaks exposure into categories such as mixers, exchanges and iGaming instead of showing only a single number. The result provides investigation context but should not be treated as a legal conclusion or used without understanding the underlying methodology.
Which transaction export formats are supported?
Ledger and banking transactions can be saved as PDF, CSV or XLS files. PDF is useful for stable review evidence, while CSV and XLS are generally more practical for reconciliation, filtering and accounting analysis.
Which new digital assets were added in July 2026?
Support was added for Bitcoin, Litecoin, Bitcoin Cash and Ripple/XRP. Companies should still apply their own treasury, accounting and risk approval process before holding or transferring any newly supported asset.
Writes for Stablerail on stablecoin treasury operations.
More about the Stablerail team- Stablecoin treasury managementApprovals, limits, yield and reporting on one balance.
- Stablecoin payoutsBatch contractor and vendor payments with screening.
- USDT vs USDCWhich stablecoin your company should settle in.
- Stablecoin finance glossaryMPC, off-ramp, travel rule and the rest, in plain English.
- Product updatesEverything we ship, month by month.

