LiqPay does not currently offer SCIM-based user provisioning. Stepwork automates LiqPay provisioning with 98% accuracy — no API required.
API-key credential model. Complexity Vector: Payments governance depends on disciplined key issuance/rotation and evidence trails.
For payments, it’s stressful when access control is essentially “who has the keys” and audits rely on manual proof. Stepwork can standardize key-handling workflows and capture evidence, which is why teams use Stepwork to automate LiqPay flows with 98% accuracy without needing an API.
No. LiqPay does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates LiqPay 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 LiqPay 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 no scim lifecycle.. Additional risks include key rotation is manual, environment keys (test/live) differ, audit evidence is manual.. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider, mirroring your organization's security posture.
See how Stepwork provisions users in LiqPay with 98% accuracy — in a 15-minute demo.
Book a Demo