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

  1. Create an Experiment: Define at least two variants, each pointing to a different connection_id with a weight (traffic allocation).
  2. Set Targeting: Optionally limit the experiment to specific currencies, countries, or payment methods.
  3. Start the Test: Activate the experiment. Reevit’s router will split traffic according to your weights.
  4. Analyze Results: View real-time success rates, latency, and costs per variant.
  5. 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

  1. Sufficient Volume: Run tests long enough to gather statistically significant data (usually 1,000+ transactions per variant).
  2. One Variable at a Time: Only compare connections; don’t change targeting rules mid-experiment.
  3. Start with Low Traffic: Use traffic_percentage to initially test with 10-20% of traffic, then scale up.
  4. Apply Learnings: After completing a test, create a Routing Rule to make the winning connection your primary.

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.