No. Rivet works with your existing processor and never touches the flow of funds. We review the data you already send with each transaction and show you which fixes will lower your interchange rates. Nothing about your processor, contracts or settlement changes.
We analyze your historical transaction data against card network rules and flag exactly where downgrades, missing data, or misclassifications are costing you, broken down by processor, card type, and transaction category.
RivetOptimize fixes the specific data issues that cause interchange downgrades, in 50ms or less, before the transaction reaches your processor. It never touches pricing, routing or your checkout experience.
You'll see the opportunity during the initial audit. How fast it becomes recovered dollars depends on the fix. Data fixes that RivetOptimize applies start saving money as soon as they go live after your testing period, and the savings add up with every transaction after that. Billing errors that need a credit from your processor follow their timeline, not ours.
Getting started just needs someone who can generate read-only API credentials for your processor, usually a developer, and it takes minutes, not a sprint. Day to day, whoever owns payments performance on your team, a payments lead, a finance owner, or a product manager, is who typically works with the findings.
Every payload that reaches our API is tokenized before it gets to us. We never receive raw cardholder data, and any call that does contain untokenized cardholder data is rejected automatically. Rivet runs on AWS, on the same certified infrastructure that secures some of the largest platforms in payments.