Guides
Start typing to search…

Single Merchant Setup

Using a single merchant account is the simplest way to process payments in Vrio. All transactions for your campaign will process through one payment gateway, using that merchant's default currency and settings.

When to Use Single Merchant

Best for:

  • Getting started with payment processing
  • Single currency operations
  • One trusted payment processor
  • Lower transaction volumes
  • Straightforward business models without complex routing needs

Prerequisites

Before configuring your campaign, you need:

  • At least one merchant account configured in Vrio
  • The merchant must support your desired payment methods (credit card, PayPal, Apple Pay, etc.)
  • The merchant must support your desired card types (Visa, Mastercard, Amex, etc.)

How Single Merchant Works

Transaction Flow:

  1. Customer places order on your campaign
  2. Transaction automatically routes to the configured merchant
  3. Merchant processes payment using their gateway
  4. Result returned to customer

Currency:

  • All transactions use the merchant's default currency
  • Currency can be overridden via API if needed

No Routing Logic:

  • No merchant selection decisions
  • No failover or redundancy
  • Direct, straightforward processing

Setting Up Single Merchant on Campaign

Step 1: Navigate to Campaign Settings

  1. Go to Campaigns
  2. Select your campaign (or create a new one)
  3. Navigate to the Settings or Payment section

Step 2: Configure Payment Type

  1. Set Payment Type to Merchant
  2. Select your merchant from the dropdown
  3. Save changes

Step 3: Verify Configuration

Check that:

  • Merchant is active
  • Payment methods are configured on the merchant
  • Card types are configured on the merchant
  • Currency is set correctly on the merchant

Step 4: Test

  1. Process a test transaction through your campaign
  2. Verify payment processes successfully
  3. Check currency displays correctly
  4. Confirm payment method and card type restrictions work

Payment Methods & Card Types

The merchant's configuration determines what payment options are available:

Payment Methods:

  • Only payment methods enabled on the merchant will be available
  • Example: If merchant only has credit card enabled, PayPal won't work

Card Types:

  • Only card types enabled on the merchant will be available
  • Example: If merchant doesn't accept Amex, those transactions will decline

To add payment methods or card types:

  • Edit the merchant account configuration
  • Enable the desired payment methods and card types
  • Save changes

Currency

Default Behavior:

  • Transactions use the merchant's default currency
  • Set during merchant configuration

API Override:

  • Pass currency_id parameter to process in different currency
  • Merchant must support the requested currency
  • Transaction will decline if currency not supported

Upgrading to Payment Router

As your business grows, you may want to upgrade to a payment router for:

  • Redundancy and failover protection
  • Multiple currency support
  • Higher transaction volumes
  • Advanced routing logic

Migration Steps:

  1. Set up additional merchant accounts
  2. Create a payment router
  3. Add your merchants to the router
  4. Update campaign to use router instead of single merchant
  5. Test thoroughly before switching production traffic

Note: You can switch back to single merchant at any time.

Troubleshooting

Transaction Declined - Merchant Not Active

Issue: Merchant account is inactive

Solution:

  • Go to Merchants
  • Verify merchant is active
  • Activate merchant if needed

Transaction Declined - Payment Method Not Supported

Issue: Merchant doesn't support the payment method (e.g., PayPal, Apple Pay, credit card)

Solution:

  • Edit merchant configuration
  • Enable the required payment method
  • Save changes

Transaction Declined - Card Type Not Supported

Issue: Merchant doesn't support the card type (e.g., Amex, Discover)

Solution:

  • Edit merchant configuration
  • Enable the required card type
  • Save changes

Currency Mismatch

Issue: Trying to process in currency merchant doesn't support

Solution:

  • Edit merchant configuration to add currency support, or
  • Use API to override with supported currency, or
  • Switch to different merchant that supports the currency

Processing Limit Reached

Issue: Merchant hit monthly revenue cap

Solution:

  • Increase merchant processing limit, or
  • Switch to payment router with multiple merchants for automatic load balancing

Best Practices

For Production:

  • Ensure merchant is thoroughly tested before going live
  • Monitor merchant performance and approval rates
  • Set up processing limits if needed to manage risk
  • Have backup plan if merchant experiences downtime

For Testing:

  • Use test credentials for merchant
  • Process test transactions before going live
  • Verify all payment methods and card types work
  • Test currency handling if using multiple currencies

For Scaling:

  • Monitor transaction volumes
  • Watch for approaching processing limits
  • Plan migration to payment router as you grow
  • Consider redundancy needs early

Related Documentation


Updated about 3 hours ago