Solutions

Acquirers & Sponsor Banks

You own every merchant in your portfolio, including the ones your ISOs boarded. Slyce360 gives acquirers and sponsor banks continuous, transaction-level oversight, so a rogue merchant shows up in your data before it shows up in a consent order.

The risk you carry

When a merchant goes rogue, everyone asks who processed the payments.

Underwriting a merchant means taking responsibility for its behavior, whether you know about it or not: its products, marketing, affiliates, fulfillment and customer service. That exposure falls into five areas.

  • RegulatoryThe FTC, CFPB, state attorneys general and banking regulators increasingly look past the merchant to the institution that processed its payments.
  • LitigationClass actions name the acquirer, the ISO and the sponsor bank alongside the merchant, often after the merchant is insolvent, offshore or gone.
  • ComplianceVisa and Mastercard hold the acquirer responsible for every merchant. VAMP and GMAP score the health of your whole portfolio.
  • FinancialWhen a merchant can’t cover its chargebacks, the loss is yours, and reserves can vanish when a merchant’s assets are frozen.
  • ReputationalThe headline rarely stops at the merchant. Reporters, regulators and plaintiffs all ask who processed the payments.
Read: What are the five risk vectors for acquirers?

Enforcement in the payments chain

It’s already happening.

Regulators, courts and card networks have held banks, processors and ISOs responsible for the merchants they enabled. In almost every case, the early warning signs were in the transaction data first.

$4.85MReputational

Nuvei

September 2026 · FTC

Settled charges that it kept accounts open for merchants it knew or should have known were deceptive, including an offshore tech-support scheme it processed more than $30M for. The headlines followed.

$12MCompliance

Humboldt Merchant Services

September 2026 · FTC

Mastercard reviews found load balancing across thousands of subscription accounts years before the FTC cited more than 1,000 shell merchants. A federal court entered a $12M judgment and a permanent ban on high-risk processing.

$5MRegulatory

Paddle

June 2025 · FTC

Settled allegations that it processed for deceptive tech-support schemes using fake virus alerts to sell auto-renewing subscriptions. Paddle is permanently banned from processing for that category of merchants.

$46.8MFinancial

Qualpay

2020 · FTC

Boarded MOBE after at least seven processors declined it. Within two months MOBE ran nearly five times its approved volume with a 2.54% chargeback ratio. The judgment was suspended only because Qualpay could not pay it.

$37.5MLitigation

Zions First National Bank

2016 · RICO class action

Settled Reyes v. Zions after plaintiffs alleged the bank processed for fraudulent telemarketers, with more than 500,000 consumer accounts debited without authorization. The case went to the Third Circuit before settling.

Summarized from public FTC actions and court filings, as covered in What are the five risk vectors for acquirers? Allegations are as described in those actions; Humboldt and Nuvei settled without admitting or denying them.

ISO oversight

Your ISOs’ merchants are your merchants.

Whether an ISO is wholesale or retail, the card networks and regulators trace the merchant back to your BIN. Slyce360 gives you one view across every ISO, merchant and MID, with alerts that roll up to you.

Wholesale ISOs

They underwrite and price their own merchants and take on the liability. But when an ISO can’t cover the loss, it lands on your BIN and your bank. You need to see their portfolio as it changes, not just at the annual review.

Retail ISOs

You underwrite the merchants and carry the risk, but the retail ISO owns the relationship, and its incentives don’t always match yours. Its business runs on new accounts and commissions, not on managing the risk those accounts bring to your portfolio.

Analytics below the MID

With Slyce360, you’ll see what your current reporting can’t show you.

Acquirer and gateway reports stop at the merchant ID. Slyce360 brings merchant CRM data alongside your payments data, so you can see which affiliate, offer or campaign is driving the risk.

Typical reporting
Slyce360
Level of detail
Totals by MID
Every transaction, tied to the affiliate, campaign, product and landing page behind it
Timing
After month-end, or when a card-brand notice arrives
Rolling 7- and 30-day measures, with daily alerts as trends develop
Portfolio view
Separate fraud and dispute reports
Fraud and disputes together by MID, merchant, ISO and portfolio, grouped any way you’d like
Scam signals
Rarely tracked
Approval-rate and refund-plus-chargeback rate oddities on new merchants, the signals SMMP is built on
Mitigation
Invisible to the acquirer
Alerts and refunds matched to the transactions they were meant to protect, with early alerts on mitigation leakage
Compliance Enforcement
Email threads and spreadsheets
Every alert becomes a work ticket with an owner, a prescriptive plan and an activity timeline

Litigation & regulatory defense

When someone asks what you knew, show them.

Regulators and plaintiffs’ attorneys ask the same questions: when did you see the problem, and what did you do about it? With Slyce360, every alert, owner, update and corrective action is recorded with a date, so your oversight is documented, not reconstructed.

And because problems surface while they are still small, the strongest record is the one where the fine, the lawsuit and the headline never happen.

See your portfolio the way a regulator would.

Talk to our team about continuous oversight of your ISOs and merchants.

Schedule a consult