Routing A/B Tests
A/B tests let you compare the performance of different PSP connections under real traffic. Instead of guessing which provider is best for a region or payment method, you can run a controlled experiment and let the data decide.A/B Tests are an advanced feature for optimizing your payment stack. Use them when you have multiple connections for the same region and want to find the highest-performing option.
π― When to Use A/B Tests
βοΈ How It Works
- Create an Experiment: Define at least two
variants, each pointing to a differentconnection_idwith aweight(traffic allocation). - Set Targeting: Optionally limit the experiment to specific currencies, countries, or payment methods.
- Start the Test: Activate the experiment. Reevitβs router will split traffic according to your weights.
- Analyze Results: View real-time success rates, latency, and costs per variant.
- Declare a Winner: Complete the test and apply the winning connection to a permanent routing rule.
π οΈ Creating an A/B Test
Via SDK
π Field Reference
π Test Lifecycle
Managing the Lifecycle
π Analyzing Results
Fetch the comparison report:β Best Practices
- Sufficient Volume: Run tests long enough to gather statistically significant data (usually 1,000+ transactions per variant).
- One Variable at a Time: Only compare connections; donβt change targeting rules mid-experiment.
- Start with Low Traffic: Use
traffic_percentageto initially test with 10-20% of traffic, then scale up. - Apply Learnings: After completing a test, create a Routing Rule to make the winning connection your primary.
π Related Resources
Smart Routing
Apply your test results as permanent routing rules.
Connections
Manage the PSP accounts youβre comparing.
Payments
See how individual payments are attributed to test variants.

