- If a buyer requires posted, fixed pricing tiers and maximum upfront price transparency
- Resolve uses custom, risk-based pricing and a sales-led procurement model, which can make price benchmarking more complex.
- If an organization’s brand or customer relationships are extremely sensitive to third-party collections communications
- Even when financing is structured as net-terms funding rather than traditional collections, the buyer-facing communications and escalation model should be reviewed for brand impact.
- If the primary need is an enterprise invoice-to-cash suite rather than net-terms financing
- Vendors focused on invoice presentment and comprehensive AR controls may be a better fit for that core problem.
- If a platform/marketplace requires deep API control over underwriting and the credit lifecycle
- API-first embedded finance providers may be a better fit for programmatic control and custom workflows.
- If ERP or ecommerce data hygiene is poor and the organization cannot invest in integration and process cleanup
- Resolve’s documentation notes invoice merging and cross-system flows; poor data quality can delay implementation and reduce ROI.
- Current limitations acknowledged in public materials
- Pricing is not published as standard tiers; the vendor uses custom plans and risk-based fees.
- Credit line sizes are discretionary and not guaranteed per pricing page fine print.
- Roadmap visibility
- No public roadmap dates were found in the accessible sources.
- Scale limitations
- No explicit public documentation of scale limits was found in the accessible materials.
- Security and compliance documentation gaps (public info gaps)
- SOC 2 Type II is claimed; the public trust center did not provide directly accessible evidence or report scope in the automated crawl used for this review.
- GDPR/CCPA and PCI specifics for Resolve Pay were not clearly documented in the accessible sources.
- API and integration constraints
- API uses OAuth 2.0 client credentials and a sandbox environment is available.
- Developer documentation describes invoice merging and ecommerce event flows, which can create operational complexity for some implementations.