- Company sizes or stages where this product is overkill or insufficient
- Early-stage SMBs with low transaction volumes may be better served by providers with simpler, published pricing and lower onboarding overhead.
- Industries or use cases where competitors are clearly superior
- Businesses primarily needing integrated spend management, corporate cards, and embedded payment acceptance workflows may prefer platforms with broader built-in capabilities.
- Technical requirements that this product may not meet
- If procurement requires publicly available SOC 2 Type II reports, SCIM provisioning documentation, or detailed penetration-test summaries, the publicly available evidence for these controls was insufficient in the reviewed sources and will require NDA/security review and direct vendor confirmation.
- Budget constraints
- If negotiated pricing or variability in effective FX spreads is unacceptable, alternatives with published fee schedules can reduce cost uncertainty.
- Specific workflows or integrations where the product may fall short
- If an organization needs a very large marketplace of prebuilt integrations (accounting, e-commerce, cards/spend, expense management), procurement should validate Ebury’s integration catalog and compare it with alternatives prior to commitment.
- Red flags in the buying process
- Lack of an upfront fee schedule exhibit in the contract.
- Unclear SLAs for support responsiveness during urgent payment incidents.
- Over-reliance on verbal assurances from account managers without written contract exhibits or SLAs.
- Current limitations acknowledged by the vendor
- Public-facing pages emphasize security and pricing clarity at a high level but do not provide exhaustive enterprise security documentation (public SOC 2 reports, detailed pen-test results, or complete IAM feature lists were not found in publicly accessible sources reviewed).
- Features on the roadmap
- Product roadmaps were not systematically published in the sources reviewed.
- Scale limitations
- Scale limits and throughput are not publicly quantified; reference calls and contractual SLAs are recommended for evaluation.
- Security or compliance gaps
- SOC 2 Type I/II reports were not located in the publicly accessible sources reviewed.
- ISO 27001 certification is documented in vendor materials for certain entities.
- API limitations or integration constraints
- API documentation exists, but rate limits, feature coverage by region/entity, and support models are not fully detailed in publicly available materials.