Default onlyCopied!

Always routes payments to a single, designated primary processor. Simple to set up, but doesn’t adapt to failures or performance changes.

Default with recency fallbackCopied!

Attempts the default processor first, but falls back to the most recently added processor if the initial attempt fails—helpful in dynamic or inconsistent payment environments.

Random uniformCopied!

Distributes payment attempts evenly across all available processors. Useful for load balancing or testing processor performance without bias.

Random weightedCopied!

Routes payments based on pre-configured weights per processor (e.g., 65% to Processor A, 30% to Processor B, 5% to Processor C). This allows controlled testing or prioritization of preferred processors.

CustomCopied!

Harnesses AI and rich historical data—like geography, transaction type, time of day, and card BIN—to dynamically route each transaction to the processor most likely to succeed, optimizing for both acceptance and cost-efficiency. To explore a custom routing strategy tailored to your business, reach out to us at support@getopenpay.com.