Exigo vs ByDesign vs DirectScale: MLM Payment Features
Industry Payment Guides

Exigo vs. ByDesign vs. DirectScale: Comparing MLM Software on Payments

Exigo vs ByDesign vs DirectScale for MLM payments: the vendor questions on gateways, autoship retry limits, commission payouts and card vaults.

Woman with red hair in a bun typing on a laptop at a wooden dining table in a bright home

Photo: Pixabay

On this page 7 sections
  1. Why Payments Decide Exigo vs. ByDesign vs. DirectScale
  2. Gateway Support Decides Which Processors You Can Use
  3. Autoship Retries Have Hard Network Limits
  4. Commission Payouts Should Follow Settlement, Not Orders
  5. Your Card Vault Decides Whether You Can Leave
  6. Price the Platform's Payment Fee and Exit Terms
  7. A Payments Scorecard for Exigo, ByDesign and DirectScale

Key takeaways

  • Daily retries on a declined autoship pass Visa's long-standing limit of 15 reattempts in 30 days by about the third week. Retry schedules need to be set by the merchant.
  • Mastercard charges for retries beyond 35 in 30 days and for any retry after a do-not-retry advice code.
  • If your saved cards sit in a vault tied to your processor, losing that processor can take your autoship base with it unless your contract requires an export.
  • Pay commissions from settled funds after reserves, not from the sales report.

You can't choose between Exigo, ByDesign and DirectScale on payments by reading their feature pages. All three sell direct selling back office software that runs distributor genealogy, commissions, replicated sites and autoship, and all three can take a card. Choose the one that gives you the best written answers on four payment jobs:

  • connecting to the processor you pick
  • keeping autoship charges approved within Visa and Mastercard retry rules
  • paying commissions out of money that has actually settled
  • letting your saved cards leave if your processor drops you

We don't publish a feature grid ranking the three. Their gateway lists and contract terms change, and much of what you end up with depends on what you negotiate. The questions below, and the answers you should expect, stay useful even when a vendor's product changes.

Why Payments Decide Exigo vs. ByDesign vs. DirectScale

For an MLM, payments are a bigger part of the platform decision than for most businesses. Underwriters classify network marketing as high risk. The main reasons are starter-kit chargebacks and the income and health claims distributors make. Many mainstream payment companies restrict the model outright, as our breakdown of whether Stripe, Square or PayPal allow MLM businesses explains. An MLM's processor relationship can end on short notice. If the platform is wired to one gateway, or your saved cards sit in a vault you can't export, losing the processor also means losing your autoship base. For in-person sales by your field, see our guide to card readers for direct sales consultants at home parties.

A network marketing platform also runs several money flows at once, and each one reaches the processor differently:

  • Retail customers order through distributors' replicated sites.
  • Distributors place wholesale orders at member prices.
  • Enrollment puts the first charge, usually a starter kit, on a new distributor's card.
  • Autoship charges a stored card on a schedule.
  • Commission payouts send money back out to the field.
  • Refunds and chargebacks have to reverse the commissions earned on the original order.

Weak implementations fail at the last item. When an order is refunded or charged back, the volume credited to the upline should come off. Any commission already paid on that order should be clawed back or netted against the next run. If the payment module and the commission engine don't share that event cleanly, you end up paying commissions on money you no longer have. In each demo, ask the vendor to walk a starter kit refund from the first click through to the commission adjustment. Then check what you hear against your own policy on starter kit refunds and new-distributor chargebacks.

Gateway Support Decides Which Processors You Can Use

Sales calls tend to blur three terms:

  • Your merchant account is your approval from an acquiring bank to accept cards.
  • A processor moves transactions between that bank and the card networks.
  • The gateway is the software connection that sends each transaction from your platform to the processor.

Your MLM software never talks to Visa directly. It talks to a gateway, so the gateways a platform supports determine which processors you can use.

Ask which gateways are live in production today. Don't count "on the roadmap" or "we can build it." A platform connected to widely used payment gateways such as NMI or Authorize.net gives you more acquirers to choose from, because many high-risk acquirers board merchants through gateways like those.

Some platforms steer clients to a preferred payment partner. That's a reasonable starting point if the partner actually underwrites MLMs. The problems start when the preferred partner is the only option the platform supports, or when the contract penalizes you for leaving. Get answers in writing on these points:

  • Can the platform route to more than one merchant account by rule, for example by country or product line?
  • If you need a new gateway connector, who pays to build it and how long does it take?
  • Does the platform add its own per-transaction fee on top of your processor's pricing?
  • Can an admin switch the default gateway in a setting, or does that take a support ticket and a development sprint?

A backup merchant account is a legitimate plan if both acquirers have underwritten your actual business and know the other account exists. Splitting volume across accounts to stay under chargeback monitoring thresholds is a different thing. Acquirers and networks treat it as evasion. It can lead to termination and to a listing on the industry databases that acquirers check before they approve a merchant. Flexible routing should make the honest setup easy. It shouldn't help you hide anything.

Autoship Retries Have Hard Network Limits

In many compensation plans, autoship is both a major source of revenue and the thing that keeps distributors qualified for their rank. A failed charge can lose you the order and drop the distributor out of a commission tier. Four parts of the autoship engine matter more than how the storefront looks.

Flag the First Charge as the Start of a Recurring Agreement

Visa's stored credential framework separates charges the cardholder starts from charges the merchant starts. Under that framework, a recurring payment is one in a series processed at set intervals no more than one year apart, according to Moneris's summary of the rule. Visa's own framework document says regularly scheduled standing-instruction transactions carry the recurring indicator "R."

The Merchant Risk Council notes that each later charge should reference the original transaction: Visa's Network Transaction ID or Mastercard's Trace ID. The framework also requires you to tell cardholders how their stored card will be used, notify them before future charges and let them cancel, as CardConnect's compliance page summarizes. Ask each vendor to show where the platform sets these indicators. Your processor can confirm the exact fields it expects.

Stay Under Visa and Mastercard Retry Caps

These are network rules, not processor pricing. Visa's excessive reattempts rule has long limited reattempts of a declined transaction to 15 within any 30-day period. The 16th attempt and beyond count as excessive, and Nets notes that those attempts draw a fee. Visa also groups decline codes into categories. According to Payway, any reattempt after a Category 1 decline, such as a closed or stolen-card account, counts as excessive. PayKings reports that the April 2026 edition of the Visa rules raised the cap to 20, while many processor pages still say 15. Build your schedule to the lower number until your processor confirms which one applies to you.

Mastercard counts differently. Braintree's notice of the change set the limit at 35 retries. Eye On Annapolis reports that Mastercard started charging in November 2023 for more than 35 retries of a transaction within 30 days. The fee started at $0.15 per excess attempt, rose to $0.30 in January 2024 and reached $0.50 in January 2025. The same charge applies to a retry after one of Mastercard's do-not-retry merchant advice codes.

Merchants often break these rules through platform defaults. Here's an illustrative case: an autoship declines for insufficient funds on the 1st, and the platform retries once a day. By the 16th it has made 15 reattempts, the most Visa's long-standing rule allows, and a retry on the 17th would be excessive with half the month still to go. A merchant-set schedule avoids that. For example, retrying on days 2, 4, 7 and 10 uses four attempts, stops on any hard decline and finishes before a month-end commission close. Ask each vendor whether you can set the schedule, whether it reads Visa decline categories and Mastercard advice codes, and whether it counts attempts per card.

Account Updater and Distributor Recovery

Visa Account Updater and Mastercard Automatic Billing Updater supply new card numbers and expiration dates when an issuer reissues a card. According to the Global Payments developer documentation, they also tell merchants when a card has been canceled. Your gateway or processor has to subscribe to these services, and the platform has to write the updates into distributor profiles. Ask who runs the updater and how often it checks your stored cards.

When retries fail, the platform should automatically send the distributor a secure link that opens their autoship payment settings. Every extra step between the message and the card form costs you recoveries.

Worked Example: What Better Recovery Is Worth

These numbers are illustrative, not industry data. Assume:

  • 5,000 active autoships averaging $90 a month
  • 4% fail on the first attempt

That's 200 failed orders, or $18,000 in monthly sales. If the updater and compliant retries recover half, 100 orders worth $9,000 are still lost each month, and the upline loses the commissionable volume tied to them.

Now suppose one vendor's engine recovers 60% instead of 50%. That's 120 orders recovered instead of 100. The extra 20 orders a month are worth $1,800, or $21,600 a year at the same ticket, before you count the distributors who keep their rank. Ask each vendor for recovery reporting from a live client, with the client's name removed.

Commission Payouts Should Follow Settlement, Not Orders

MLM commission software calculates what each distributor earned. Paying them is a separate job, and that's where cash-flow problems start.

On calculation, the question is timing. Commissions should run on orders that are past the window when most refunds and chargebacks arrive. If they don't, the platform should hold back a portion to cover reversals. Ask whether you can set hold periods by order type, because a starter kit carries more chargeback risk than a distributor's sixth autoship.

On payouts, ask how the money reaches distributors. Domestic payouts usually go by ACH direct deposit. International members may need a payout card or a third-party payout provider, so check which providers the platform supports in the countries where you have distributors. Year-end tax forms are a tax matter. Confirm filing thresholds and rules with a qualified tax professional rather than trusting a software default.

Then find out who funds the payout account and when. If your acquirer holds a rolling reserve, which is common for MLMs, part of your card revenue arrives later than the sales report suggests. Ask your processor how much the reserve holds back and when each portion is released, then schedule payout dates around actual deposits.

Underwriters also read your compensation plan, and the back office configuration has to match the plan you submitted. If the platform pays heavily on enrollment volume while your submitted plan emphasizes retail sales, expect questions. Check the compensation plan red flags underwriters look for before you configure anything.

Your Card Vault Decides Whether You Can Leave

When a distributor saves a card, the full card number goes into a secure vault and your platform keeps a token, a stand-in value. A token usually works only with the vault that issued it.

Where the card vault livesWhat happens when you switch processors
A gateway tied to your processorCards must be exported to the new provider through a secure migration
The MLM platform's own vaultCards can stay if the platform supports your new gateway
An independent third-party vaultCards stay; you point the vault at the new gateway

When everyone cooperates, a migration is routine. The old provider sends encrypted card data to the new one, the new provider issues fresh tokens, and the platform maps them to distributor profiles. Card security codes don't come along. The PCI Security Standards Council's FAQ on card-on-file payments says PCI DSS prohibits storing them for recurring or card-on-file use, and it notes that those transactions don't need the codes anyway. Network tokens, if you use them, may need to be provisioned again.

Migrations usually stall over contracts. Your agreements with the platform and the gateway should say that the card data belongs to you and will be released to a PCI-compliant provider on request, with a set deadline and fee. Without that language, a terminated merchant can wait weeks while autoships fail, and some distributors who are asked to re-enter a card never do. Ask each vendor about the last time a client moved cards out of their system, not into it.

Price the Platform's Payment Fee and Exit Terms

Direct-selling platforms rarely publish their pricing, so compare how the pricing is built as well as the total. Find out:

  • whether the monthly fee is flat or rises with active distributor counts
  • what implementation and comp-plan configuration cost
  • whether payments carry a platform fee on top of your processor's rates, and whether that fee changes if you bring your own processor

In the contract, check the term length, auto-renewal, termination rights and exit assistance. Exit assistance should cover exports of genealogy, order history, commission history and the card vault.

Your comp plan's complexity drives the implementation timeline. Before cutover, run commissions on both the old and new systems for at least one full period and reconcile every difference. Have your merchant account approved and your gateway tested before launch day.

A Payments Scorecard for Exigo, ByDesign and DirectScale

Send all three vendors the same questions and score their written answers.

QuestionA strong answer
Which gateways are live in production?A named list that includes gateways your acquirer supports
Can we route to more than one merchant account?Yes, by rule, without custom development
How are autoship retries configured?A schedule you set, with attempt counts under Visa and Mastercard caps and hard-decline stops
Are stored-credential indicators set on every autoship?Yes, with the original transaction ID referenced
Who runs account updater?A named Visa and Mastercard updater service, with update reports
How are commissions reversed on refunds and chargebacks?Automatic clawback or netting, with an audit trail
Where does the card vault live, and who owns the data?You own it, and the export terms are in the contract
Is there a platform fee on payments?Disclosed in writing

Before you commit to any of the three, get your processor lined up. Gateway flexibility doesn't help if no acquirer has approved your business. If you need a high-risk merchant account that connects through gateways such as Authorize.net or NMI, request a free quote and a MannyPay specialist will respond within one business day. Have your compensation plan and refund policy ready, along with an income disclosure statement that meets processor expectations.

Sources

  1. Visa: Improving Authorization Management for Transactions with Stored Credentials
  2. Moneris: Visa Stored Credential Transaction Framework
  3. CardConnect: Visa and Mastercard Stored Credential Transaction Framework Mandate
  4. Merchant Risk Council: Card-on-File Done Right
  5. Nets: Visa Fines on Attempts to Complete Already Declined Transactions
  6. Payway: Understanding Visa's Excessive Reattempts Rule
  7. PayKings: Visa and Mastercard Card Retry Rules
  8. Braintree: Mastercard Network Updates (Excessive Authorization Attempts)
  9. Eye On Annapolis: How Technology Can Help High Risk Merchants Improve Authorization Rates
  10. Global Payments Developer Portal: Account Updater
  11. PCI Security Standards Council: FAQ 1280, Can Card Verification Codes Be Stored for Card-on-File or Recurring Transactions?

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading