Finance · Okta coverage
i2c and Okta: SSO, SCIM and offboarding
Credit, debit and prepaid card issuing and processing platform. No SCIM provisioning found.
SCIM pricing for every app →What Okta covers for i2c, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the i2c account lifecycle.
Not in the Okta Integration Network.
StitchOps covers 8 of 8 capabilities for i2c.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | No SAML or OIDC in the OIN. | Enterprise password management signs users in to i2c with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares i2c logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | No account creation in the OIN. | Creates the i2c account with the right role on day one, anywhere a person can log in and act. |
| Movers | No account updates in the OIN. | Changes i2c roles and access when someone changes jobs, anywhere a person can log in and act. |
| Leavers | No deprovisioning in the OIN. | Removes i2c access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | No password rotation in i2c. | Changes the i2c password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove i2c accounts. | Pulls the i2c user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside i2c. | Step level evidence for every action StitchOps takes in i2c. |
Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to i2c with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares i2c logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the i2c account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes i2c roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes i2c access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in i2c.
StitchOps
Changes the i2c password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove i2c accounts.
StitchOps
Pulls the i2c user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside i2c.
StitchOps
Step level evidence for every action StitchOps takes in i2c.
Okta coverage from the Okta Integration Network, read October 10, 2026. i2c has no OIN listing. StitchOps for Okta →
SCIM and API tax
What i2c charges to automate accounts.
We found no SCIM provisioning for i2c: the Okta Integration Network lists no provisioning for it, and i2c does not publish SCIM support. Ask the vendor before you count on it.
Pricing notes
Added for the financial services app catalog from vendor research (high confidence, vendor i2c Inc.). No SCIM found: no provisioning in the Okta Integration Network as of 2026 to 10 to 10 and no published SCIM support (rule set by Kyle 2026 to 10 to 10).
Last verified 2026-10-10 (estimate). SCIM pricing for every app · Method
Estimate i2c and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate i2c accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the i2c account with the right role when your HR system or identity provider says someone starts.
Movers
Change i2c roles, teams and access when someone changes department or manager.
Leavers
Remove i2c access the same day someone leaves, and free the seat.
Access checks
List who can log in to i2c on a schedule, with evidence for the audit.
Common questions.
Does i2c support SCIM?
Not that we found. The Okta Integration Network lists no provisioning for i2c, and i2c does not publish SCIM support, so accounts are created and removed by hand or by a tool that works in i2c the way an admin would.
Can i2c accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes i2c accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is i2c in the Okta Integration Network?
No. As of October 10, 2026, the OIN has no listing for i2c. Okta can sign users in only through a custom app if i2c supports SAML or OIDC, and has no connector to manage i2c accounts.
Can Okta deprovision i2c users?
Not through an OIN connector. StitchOps removes i2c accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate i2c passwords when someone leaves?
StitchOps logs in to i2c, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.