Skip to main content

​
What are Merchant Settings?

Merchant Settings are account-level configuration options that control how Revolv3 processes payments for your merchant account. They provide defaults and enable/disable features across all your transactions. Why they matter:
  • Set defaults: Values used when you don’t specify them in API requests
  • Enable features: Turn on/off features like network tokenization, ACH Verification Service, etc.
  • Configure behavior: Control how payments are processed, retried, and handled
  • Security: Configure trusted domains, etc.

​
Key Settings Overview

​
Order Processing Channel (Merchant Details section)

What it is: Defines how the transaction is being processed (e-commerce, mail order, etc.) Default behavior: Used as a fallback when an invoice doesn’t specify orderProcessingChannel When you need it: Typically only if you have processor-specific requirements Options: ECOMMERCE (default), MOTO (Mail Order/Telephone Order)

​
Payment Processor

What it is: Which payment processor (WorldPay, Adyen, Nuvei, etc.) handles transactions by default Why it matters: Determines which processor is used Configure in: Merchant Settings in the portal

​
Dynamic Descriptor

What it is: Default text that appears on customer credit card statements Default behavior: Applied to all transactions unless overridden on individual invoices Example: “ACME STORE” appears on all customer statements Learn more: Dynamic Descriptor Guide

​
Trusted Hostnames / Checkout Origins

What it is: Domains allowed to create checkout sessions and load hosted/embedded checkout Why it matters: Security feature—only authorized domains can use checkout Configure in: Merchant Settings → Integration Profile → Trusted Checkout Hostnames Learn more: Checkout Guide

​
Processor Settings

Processor configuration determines which processor(s) handle your transactions: What’s configured:
  • Processor credentials (API keys, merchant IDs)
  • Merchant codes
  • Descriptor defaults
  • Processor-specific toggles (like Account Updater)
Where to configure: Merchant dashboard (Settings → Merchant Settings → Processor Settings) Note: Processor-specific IDs and configuration screens are managed

​
Feature Toggles

​
Network Tokenization

What it does: When enabled, credit card details are tokenized. The resulting network token is retained for future transactions. Why enable it:
  • Better security
  • Higher approval rates
  • Cards stay current automatically
How to enable: Merchant Settings → Network Tokenization Also requires: Enable token usage in processor configuration

​
Eligibility Check

What it does: Performs additional verification before processing payments When to use: Useful for validating subscription continuity in your system How it works: Revolv3 checks eligibility before processing payment Configure in: Merchant Settings → Eligibility Check

​
ACH Verification Service

What it does: Selects which ACH verification provider to use (GIACT or WorldPay) Why it matters: Different providers have different verification capabilities Options: GIACT or WorldPay (only one can be active) Configure in: Merchant Settings → ACH Verification Service Learn more: Test ACH Verification

​
Recurring Strategies

What it does: Defines how recurring payments are handled (scheduling, retry logic, etc.) Includes:
  • When to retry failed payments
  • How many times to retry
  • Retry timing (immediate, after 1 day, after 3 days, etc.)
Prerequisite: Configure a payment processor before adding a recurring strategy Configure in: Merchant Settings → Recurring Strategies

​
Recycle Strategies

What it does: Handles automatic retries for failed card payments How it works:
  • Revolv3 attempts up to 15 retries for failed card/debit transactions
  • Only applies to soft declines (hard declines are not retried)
  • One-time payments and ACH are not recycled
Behavior: Follows the configured recurring strategy rules Configure in: Merchant Settings → Recycle Strategies Learn more: Subscription Status and Recycling

​
Shopify Store Domains

What it does: Manages connected Shopify store domains When to use: If you’re integrating with Shopify Configure in: Merchant Settings → Shopify Store Domains

​
How Settings Work as Fallbacks

​
Invoice-Level Overrides

Many merchant settings act as fallbacks when you don’t specify values in API requests. Example: If you don’t set orderProcessingChannel on an invoice, Revolv3 uses the merchant setting value. Benefits:
  • Simpler API requests (don’t need to specify everything)
  • Consistent defaults across all transactions
  • Easy to change defaults without updating code

​
Example: Order Processing Channel

Merchant setting: orderProcessingChannel: "ECOMMERCE" Invoice request (without specifying channel): 
{
  "Invoice": {
    "Amount": { "value": 10.00 }
  }
  // No orderProcessingChannel specified
}
Result: Invoice uses “ECOMMERCE” from merchant settings Invoice request (with channel specified): 
{
  "Invoice": {
    "Amount": { "value": 10.00 },
    "OrderProcessingChannel": "MOTO"  // Overrides merchant setting
  }
}
Result: Invoice uses “MOTO” (overrides the default)

​
Best Practices

  1. Set sensible defaults: Configure merchant settings to match your typical use case
  2. Override when needed: You can still override settings on individual invoices
  3. Review periodically: Check settings to ensure they match your business needs
  4. Document your settings: Keep notes on what settings you’ve configured and why

​
Common Questions

Q: Do I have to set all merchant settings? A: No, only set what you need. Defaults are provided for most settings. Q: Can I override merchant settings on individual invoices? A: Yes, many settings can be overridden per-invoice. Q: Where do I configure processors? A: In the portal under Merchant Settings → Processors. Q: How do I know what settings are available? A: Check the portal (Merchant → Settings) or use the help icon in the portal to submit a support ticket.

​
Next Steps