Product Releases

Tax payment execution, inside your product

Tax and accounting platforms can now run tax payment execution inside their own product, through a widget library you install in your own app.

Tax Payment Widget Library

Tax and accounting platforms can now run tax payment execution entirely inside their own product. Your user selects the payment, submits it, and receives confirmation without leaving your interface. Your branding, your workflow, your session. Remitian handles execution behind it, through a widget library you install in your own product.

Why it matters

Every tax and accounting platform reaches the same fork. Your users have prepared the return and reached the part where money has to move. Either you build tax payment execution, or you send them somewhere else to finish.

Sending them out is the cheaper answer, and it costs you the end of the workflow. Support questions about a payment you cannot see. Users who do not come back in the same session. A completion rate you cannot measure or improve.

Building it yourself means discovering that payment execution is not a payments problem, it is a compliance and coverage problem. Every authority has its own submission mechanism, credential model, and confirmation format. Support for one does not generalize to the next. Underneath that sits funds movement, business verification, reconciliation, audit trail, and the penalty exposure that lands on your customer when a payment fails silently.

None of that is your product. All of it stays on your backlog permanently, because coverage expands and agencies change.

Embedding is the version of that work you do not have to maintain.

Built on the API

Our API release earlier this year opened tax payment execution to platforms building on Remitian. Integration partners have been live on it since, running Remitian inside their own workflows at production volume. The embedded flow is the next step along that line: the same execution layer, with the interface now sitting inside their product rather than alongside it.

Underneath the API is the same infrastructure. Federal, state, and provincial payment authorities across the US and Canada, and SOC 2 Type II.

The widget library is live in the US today, with Canada coming soon. Everything you need is in the documentation.

If you would rather scope it against your own product first, get in touch.

Speak to an Expert

The IRS Is Retiring the Old Estimated Tax Payment Rails. Here's the Build Decision That Followed.

The IRS is dismantling the tax payment rails firms have relied on for decades, and the replacements were never designed for how firms actually move client money. Paper checks are gone, EFTPS for individuals is winding down, and the last mile is up for grabs.

The IRS Didn't Fix Estimated Tax Payments. It Just Took Away the Checkbook.

Executive Order 14247 phased out federal paper checks, pushing firms onto Direct Pay and EFTPS replacements built for a single person paying once, not a firm running hundreds of payments a month. The mandate arrived. The firm-grade replacement did not.

Where the Workflow Stops: Why We Are Building the Payment Layer Under Thomson Reuters SafeSend

For two quarters, buyers on demo calls have described the same broken shape: workflow, delivery, and prep run smoothly, then the tax payment falls out into a portal nobody wants to log into. Here is why we built the payment layer under Thomson Reuters SafeSend.

Your Tax Software Isn't the Problem. Your Clients Are.

Firms keep chasing the perfect tax-payment tool while their real bottleneck sits somewhere else entirely. Client adoption is the project the software cannot solve on its own, and the September deadline is closing the runway to figure it out.