Mercury does not currently offer SCIM-based user provisioning. Stepwork automates Mercury provisioning with 98% accuracy — no API required.
SCIM not clearly documented Complexity Vector: Regulated roles and approvals are UI-managed
It’s stressful when fintech platforms support SSO but SCIM provisioning isn’t clearly verifiable, leaving access governance manual. …which is why teams use Stepwork to automate Mercury flows with 98% accuracy without needing an API.
Mercury supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Mercury does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Mercury provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to Mercury through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is finance access governance becomes manual when scim provisioning isn’t clearly verifiable.. Additional risks include offboarding delays; role/approval sprawl; audit friction. Stepwork eliminates these risks by automating the entire provisioning workflow.
See how Stepwork provisions users in Mercury with 98% accuracy — in a 15-minute demo.
Book a DemoNo. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider via SAML, mirroring your organization's security posture.