Summary and recommendation
Returnly, the returns management platform acquired by Affirm, does not publicly document any SCIM provisioning capabilities or enterprise SSO features. Since the acquisition, enterprise authentication and user management features appear to be handled through Affirm's broader platform rather than Returnly's standalone offering. This creates significant uncertainty for IT teams managing user access to returns management workflows, as there's no clear path for automated provisioning or standardized SSO integration with identity providers like Okta, Entra ID, or Google Workspace.
The lack of documented provisioning capabilities means IT teams must rely on manual user management processes for a platform that often requires access coordination between customer service, operations, and e-commerce teams. Without automated provisioning, onboarding new team members or adjusting access permissions requires manual intervention, creating operational bottlenecks and potential security gaps when users aren't promptly deprovisioned upon role changes or departures.
The strategic alternative
Returnly has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | Unknown |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | No Okta integration documented |
| Microsoft Entra ID | Via third-party | ❌ | No Entra integration documented |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Returnly accounts manually. Here's what that costs:
The Returnly pricing problem
Returnly gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Enterprise | Custom (part of Affirm) |
Pricing structure
| Plan | Pricing | SCIM |
|---|---|---|
| Enterprise | Custom (part of Affirm) | ❌ Not available |
Key constraint: Returnly's enterprise features, if they exist, are only accessible through Affirm's broader platform sales process. There's no standalone enterprise offering documented.
What this means in practice
Without documented SSO or SCIM support, IT teams face significant operational challenges:
Additional constraints
Summary of challenges
- Returnly does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What Returnly actually offers for identity
No Enterprise SSO/SCIM Documentation
Returnly (now part of Affirm) doesn't publicly document any enterprise identity features:
| Feature | Supported? |
|---|---|
| SAML SSO | Unknown |
| SCIM provisioning | Unknown |
| OIDC SSO | Unknown |
| JIT provisioning | Unknown |
| Okta integration | ❌ No |
| Entra integration | ❌ No |
The situation: Returnly was acquired by Affirm and operates as a returns management platform. There's no public documentation for enterprise identity features, and no integrations appear in major IdP marketplaces.
What This Means for IT Teams
For a returns management platform that typically needs customer service and operations team access, the lack of documented provisioning creates manual overhead for user lifecycle management.
What IT admins are saying
Returnly's complete lack of enterprise identity documentation leaves IT teams in the dark:
Since Returnly was acquired by Affirm, finding basic enterprise identity information has become nearly impossible. The platform's documentation focuses entirely on returns management functionality with no mention of SSO, SCIM, or user provisioning.
- No public SSO or SCIM documentation available
- Must contact Affirm directly for any enterprise features since acquisition
- Unclear what identity capabilities exist, if any
- Zero transparency on provisioning options or requirements
The recurring theme
IT teams are flying blind with Returnly. Without public documentation on enterprise identity features, admins can't evaluate, plan, or implement proper user management - they're entirely dependent on vendor sales conversations to understand what's even possible.
The decision
| Your Situation | Recommendation |
|---|---|
| Small returns team (<10 users) | Manual management is workable given limited functionality |
| Testing Returnly integration | Manual management during evaluation phase |
| Enterprise with compliance requirements | Use Stitchflow: essential for audit trail and governance |
| Growing e-commerce operations (25+ users) | Use Stitchflow: automation needed for scale |
| Multi-brand or marketplace deployment | Use Stitchflow: automation strongly recommended |
The bottom line
Returnly (now part of Affirm) provides no documented SCIM support or enterprise SSO capabilities, leaving IT teams with manual user management regardless of scale. For organizations that need automated provisioning for their returns management platform, Stitchflow eliminates the manual overhead entirely.
Make Returnly workflows AI-native
Returnly has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- SSO/SCIM not publicly documented
- Acquired by Affirm
- Contact vendor for enterprise features
Documentation not available.
Unlock SCIM for
Returnly
Returnly has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


