This reviewer's identity has been verified by our review moderation team. They have asked not to show their name, job title, or picture.
Once you have navigated its non-intuitive system, you will be an asset to your employer because it defies logic and is extremely dated. Review collected by and hosted on G2.com.
We’ve generally had an up and down operational experience with XTRF, and we recently encountered a serious issue around add-on billing that prospective customers should be aware of.
XTRF charged us for API access based on an old API commercial agreement, even though the API had not been explicitly ordered as a paid feature once pricing was introduced, and there was no verifiable API usage on our side. The position communicated to us was that the API remained billable unless we explicitly emailed to opt out.
From our perspective, chargeable add-ons should require either clear activation and acceptance at the point they become paid, or documented usage (e.g. logs, issued credentials). Billing based on silence or lack of opt-out raises concerns around transparency and governance.
While XTRF eventually disabled the API going forward, the question of a refund for past charges has had to be escalated to our lawyers. If you need legal counsel to defend your interests against a service provider for a service you are not actually using, something is fundamentally wrong with how that service is being delivered.
Advice to prospective buyers:
Clarify upfront how add-ons (API, integrations, etc.) are activated, how acceptance of paid features is documented, and how usage is tracked and substantiated. Review collected by and hosted on G2.com.
Validated through LinkedIn
Invitation from G2. This reviewer was not provided any incentive by G2 for completing this review.
