A paid pilot

A paid pilot puts ActaSeal in front of one of your agents' payment flows, in your own environment, so you can see the result with your own data before you decide anything else.

What you get to see

• A decision for each payment before it runs: go ahead, stop, or send to a person.
• A record of each decision that shows any later change.
• A way for your customer to check a disputed payment for themselves.

How it runs

• Week 1: ActaSeal is installed in your test or staging environment, one agent's payment flow is connected to it, and your rules are written down with you: amount limits, allowed payees, and who approves what.
• Weeks 2 and 3: the agent runs as it normally would. Every payment it attempts gets a decision and a record.
• End of week 3: you get the results and decide whether to go further.

What your team provides

• A test or staging environment where it can be installed: one Linux machine or container.
• One engineer for about half a day to connect the agent.
• The rules you want applied, and the people who should approve the payments that need a person.

It runs inside your environment. Your payment data does not leave it. For your security team: where it runs, who holds the keys and what is shared under NDA are on the security page.

What you keep at the end

• The record of every decision made during the pilot.
• A short report: how many payments ran, how many were stopped or sent to a person, and why.
• A sample dispute that your customer or auditor can check for themselves, without you.

What success looks like

Agreed with you before week 1. For example: every payment in the pilot flow gets a decision before it runs, every payment above your limit waits for a person, and a disputed payment can be checked by someone outside your team.

Scope, timing and terms are agreed on a call.

Or write to sales@actaseal.com.