Multi-Acquiring

Smart Retry

Smart Retry automatically retries failed transactions with fallback acquirers to enhance payment success rates.

Navigate Risk Profiles

• Scenario: An online store receives an order from a customer in a high-risk region.
• Issue: The primary acquirer declines the transaction due to its risk profile.
• Solution: Reroute to fallback acquirer with flexible criteria.
• Outcome: Sale completed.

Optimize Conversion Rates

• Scenario: A sporting goods store processes a transaction.
• Issue: The primary acquirer declines the transaction due to the MCC associated with high-risk categories.
• Solution: Resubmit the transaction using an MCC relevant to retail or apparel.
• Outcome: Increased acceptance.

Enhance Customer Experience

• Scenario: During a flash sale, a customer's payment fails.
• Issue: The failure is due to a soft bank reject caused by a temporary network issue.
• Solution: Immediately retry the transaction with the same or a different acquirer.
• Outcome: Customer completes their purchase without interruption.

Handle Authentication Challenges

• Scenario: A customer's payment is declined.
• Issue: The decline is due to a soft decline from the issuer requesting Strong Customer Authentication (SCA).
• Solution: Resubmit the transaction with the necessary authentication data.
• Outcome: Payment processed successfully.

Business Model Adaptation

• Global Acquirer: Retry failed transactions with a global acquirer when local acquirers decline.
• High-Risk Profiles: Use fallback acquirers with greater flexibility for high-risk transactions.

Understanding Bank Rejects

Soft Bank Rejects

• Issue: Temporary issues that can be retried immediately.
• Example: Payment fails due to a temporary connection issue. Smart Retry resubmits the transaction.

Hard Bank Rejects

• Issue: Permanent failures that should not be retried until resolved.
• Example: Payment declined because the card is reported stolen. Do not retry until resolved with the issuing bank.

Smart Retry is particularly effective for handling soft bank rejects, increasing the likelihood of successful payment completion.

BIN Dispatching

BIN Dispatching routes transactions based on the first six digits of the card number, identifying the issuing bank and card type.

Enhance Payment Processing Efficiency

• Scenario: An online retailer in the US processes payments from both US and European customers.
• Issue: Need to save on shopper exchange costs.
• Solution: Route US credit cards to a US acquirer and European credit cards to a European acquirer.
• Outcome: Reduced exchange costs.

Optimize Transaction Costs

• Scenario: A merchant processes both debit and credit card transactions.
• Issue: Different acquirers offer better rates for different card types.
• Solution: Route debit cards to Acquirer A for lower fees and credit cards to Acquirer B for better rates.
• Outcome: Minimized costs and maximized profit margins.

Boost Approval Rates

• Scenario: The payment orchestration platform processes transactions from various banks.
• Issue: Acquirer A has higher approval rates for cards issued by Bank X.
• Solution: Route transactions from Bank X’s BINs to Acquirer A.
• Outcome: Increased successful transactions.

Cater to Regional Preferences

• Scenario: A global online store handles transactions from Europe and Asia.
• Issue: Need to cater to local banking practices.
• Solution: Route European-issued cards to Acquirer C for specialized handling, and Asian-issued cards to Acquirer D for better rates and approval.
• Outcome: Smoother processing and higher approval rates.

Manage High-Risk Transactions

• Scenario: A merchant processes transactions from high-risk regions.
• Issue: Increased risk of fraud and chargebacks.
• Solution: Route high-risk BINs to acquirers with robust fraud detection systems.
• Outcome: Mitigated fraud and chargebacks.

How It Works

The Credit Card BIN Dispatching allows you to navigate incoming transactions and send them to specific acquirers based on defined settings per MID:

• Credit Card BIN Ranges
• Issued Countries of Credit Cards

Example Configurations:

• Send all credit cards for Austria, Germany, and Switzerland to Acquirer MID A.
• Send all credit cards where the BIN is between 534500 and 534599 to Acquirer MID B.
• Send all credit cards where the BIN is between 510100 and 510900 to Acquirer MID C.
• Send all other cards to Acquirer MID D.

Integrating BIN Dispatching with Smart Retry

Combining BIN dispatching with Smart Retry creates a robust multi-acquiring strategy. Here’s how they work together:

• Initial Routing: Use BIN dispatching to route transactions to the most suitable acquirer based on card type, region, and cost considerations.
• Fallback Mechanism: If a transaction fails, Smart Retry automatically resubmits it to a fallback acquirer.
• Continuous Optimization: Analyze transaction data to refine BIN dispatching rules and Smart Retry configurations for optimal performance.

Channel Dispatching

Channel Dispatching allows merchants to distribute payments across multiple channels based on specific criteria or predefined percentages.

Channel Dispatching by Matched Criteria

Routes transactions to specific channels based on predefined criteria, such as card brand or issuing bank.

Brand-Specific Routing

• Scenario: Transactions from specific card brands (e.g., Visa, MasterCard).
• Issue: Need to optimize costs and approval rates.
• Solution: Route Visa transactions to Acquirer A for lower fees, and MasterCard transactions to Acquirer B for higher approval rates.
• Outcome: Reduced transaction costs and increased approval rates.

Regional Preferences

• Scenario: Transactions based on the issuing bank’s region.
• Issue: Need to cater to local banking practices.
• Solution: Route European-issued cards to Acquirer C for specialized handling, and Asian-issued cards to Acquirer D for better rates and approval.
• Outcome: Smoother processing and higher approval rates.

Channel Percentage Dispatching

Distributes a certain percentage of transaction traffic to different channels, each configured with specific acquirers.

A/B Testing

• Scenario: Evaluate different acquirers.
• Issue: Need to compare approval rates and transaction costs.
• Solution: Route 50% of transactions to Acquirer A and 50% to Acquirer B.
• Outcome: Data collected to determine the better-performing acquirer.

Feature Rollout

• Scenario: Test new payment orchestration platform features.
• Issue: Minimize risk during rollout.
• Solution: Test the new feature on 10% of transactions while 90% continue with the existing setup.
• Outcome: Validate the new feature with minimal disruption.

Risk Management

• Scenario: Implementing new 3DS versions.
• Issue: Need to test 3DS 2.3 while maintaining stability with 3DS 2.2.
• Solution: Route 10% of transactions to 3DS 2.3 and 90% to 3DS 2.2.
• Outcome: Informed risk management and smooth transition.

How It Works

When a payment transaction hits the gateway, it is processed according to the dispatching rule set by the merchant:

• Matched Criteria Dispatching: Routes transactions based on specific attributes like card brand or issuing bank.
• Percentage Dispatching: Distributes transactions across channels based on predefined percentages to balance load and evaluate performance.

Integrating Channel Dispatching with Smart Retry

Combining Channel Dispatching with Smart Retry creates a robust multi-acquiring strategy. Here’s how they work together:

• Initial Routing: Use Channel Dispatching to route transactions based on criteria or percentages.
• Fallback Mechanism: If a transaction fails, Smart Retry automatically resubmits it to a fallback acquirer.
• Continuous Optimization: Analyze transaction data to refine Channel Dispatching rules and Smart Retry configurations for optimal performance.