Merchant Account for MSB Business [Instant Approval]

Yes. 2Accept onboards both U.S.-based and non-U.S. MSB operators. Non-U.S. MSB businesses are placed with offshore acquiring banks in the U.K., EU, Caribbean, or APAC with multi-currency settlement in USD, EUR, GBP, CAD, AUD, and MXN for US-to-LatAm corridors. U.S. MSB entities with current FinCEN Form 107 registration and state MTL coverage qualify for domestic MIDs with next-business-day funding.

Not necessarily, but you need MTL coverage in every state where your customers and beneficiaries reside, with the exception of Montana — the only state in the US without a money transmitter statute. Approximately 49 states require MTL; bonding requirements range from $50K to $2M+ per state and capital requirements vary enormously between states. Many MSBs operate in 5–10 states because full 50-state MTL is operationally impractical. 2Accept underwrites MSBs with partial state coverage using geofencing on non-licensed states.

An MSB application typically requires your EIN, Articles of Incorporation, beneficial ownership disclosures for all 25%+ owners, voided check for settlement, 3 months of business bank statements, 3 months of processing statements (if applicable), government-issued ID for the signer, your FinCEN MSB registration number (Form 107 with current 2-year renewal date), your state-by-state Money Transmitter License coverage map (typically 5–49 states), New York BitLicense documentation if you operate as crypto-as-MSB serving NY residents, your BSA/AML written program with designated Compliance Officer, your Customer Identification Program (CIP) documentation, your OFAC SDN screening provider configuration (ComplyAdvantage or Refinitiv World-Check), your FATF Travel Rule integration evidence for transfers above $3,000 under Rule 16, your CTR filing workflow for cash equivalents above $10,000, your SAR filing audit trail, and your KYC stack configuration (Sumsub or Onfido).

No. 2Accept MSB agreements do not include early termination fees or multi-year lock-in. You may close the MSB account with 30 days written notice. The acquiring bank retains the rolling reserve for 180 days post-closure to cover any lingering fiat-side chargebacks on irreversibly settled corridor or prepaid load transactions.

Yes. FinCEN MSB registration via Form 107 is a federal prerequisite for any Money Service Business operating in the United States. The registration must be current — Form 107 expires every 2 years and must be renewed before the expiry date. 2Accept verifies your FinCEN registration number against the FinCEN MSB Registrant Search at underwriting and tracks the renewal date on a 90/60/30-day reminder cadence to keep your MID compliance-current after go-live.

Yes. 2Accept specifically underwrites MSB operators terminated by Stripe, Square, PayPal, or other processors. Full disclosure of the termination reason is required, along with a remediation plan addressing whatever caused the termination (chargeback ratio, FinCEN Form 107 lapse, incomplete state MTL coverage, Travel Rule gaps, OFAC screening failures, CTR/SAR filing delays, or descriptor flagging on MSB-restricted language). MATCH-listed MSB merchants are placed on offshore acquirers with enhanced rolling reserve terms.

No. 2Accept does not charge an application fee, underwriting fee, or setup fee on MSB accounts. You only pay transaction fees once your MSB MID goes live and starts processing card-funded send, prepaid load, or FX exchange flow. There is no fee to be reviewed by our MSB underwriting desk, and there is no fee if you are declined.

MSB rates start around 3.95% for established licensed money transmitters with full FinCEN Form 107 currency and comprehensive state MTL coverage and run higher for cross-border remittance corridor operators (US-to-LatAm, US-to-Africa, US-to-Asia), prepaid card issuers operating under bank sponsorship, crypto-as-MSB exchanges in early state MTL or BitLicense rollout, agent-network operators with elevated supervisory complexity, and offshore-placed MSBs serving sanctions-sensitive corridors, with custom interchange-plus pricing for high-volume MSBs above $500K monthly. Your final MSB rate depends on monthly volume, average ticket, chargeback ratio, KYC tier mix, sanctions exposure profile, state MTL coverage completeness, and your compliance posture across BSA/AML, FATF Travel Rule, OFAC SDN screening, and CTR/SAR filing.

Yes. After 6–12 months of clean MSB processing (chargeback ratio under 0.5%, zero OFAC hits, current FinCEN Form 107 with renewal more than 60 days out, complete state MTL coverage with no lapsed-state geofencing failures, current Travel Rule attestations, CTR/SAR filings on time), 2Accept can submit a rate review request to the acquiring bank. Successful MSB rate reviews reduce the discount rate by 0.50%–1.0% — meaningful basis points on the higher base rates that apply to MSB verticals.

Not always. 2Accept does require monthly minimum MSB processing volume in circumstances where the approval is laborious (full state MTL coverage validation across 30+ states, OFAC remediation, FinCEN guidance review for crypto-as-MSB) or the account would operate at a loss when volume is low or zero. Some acquiring banks on top-tier MSB verticals — particularly offshore acquirers serving cross-border remittance corridors — may set a $50K or $100K monthly minimum to maintain the MID. You will always pay transaction fees only on the volume you actually process.

No. 2Accept publishes a flat monthly statement on MSB accounts with your discount rate, per-transaction fee, monthly gateway fee, chargeback fee, OFAC screening fee, and Travel Rule attestation fee only. There are no PCI non-compliance surcharges, no early termination fees, no monthly minimums on standard accounts, no junk-fee line items, no separate CTR/SAR filing fees (those are bundled into the per-transaction fee), and no surcharge for FinCEN Form 107 renewal tracking.

Interchange is the wholesale fee that Visa, Mastercard, and Discover charge the acquiring bank for every transaction, typically 1.65%–2.7% on MCC 6051 quasi-cash card-not-present transactions (interchange is structurally higher on MSB activity than on retail e-commerce because of the irreversibility of corridor settlement and prepaid load). 2Accept offers both flat-rate pricing (discount rate includes interchange) and interchange-plus pricing (interchange passed through plus a fixed 1.25%–2.5% markup) for MSB merchants processing above $500K monthly. Licensed money transmitter and prepaid issuer MIDs are most commonly priced interchange-plus once monthly volume scales.

Chargeback fees on 2Accept MSB merchant accounts range from $25 to $50 per dispute depending on the account configuration, risk profile, and acquiring bank. MSB chargeback fees run higher than retail e-commerce because the underlying corridor settlement, prepaid load, or P2P transfer has already cleared into the beneficiary account or onto the reloadable card and become irreversible from the merchant side, so the acquirer absorbs more dispute-handling cost. The fee applies whether you win or lose the representment. Ethoca and Verifi alerts prevent the vast majority of disputes from becoming chargebacks.

Most MSB merchant accounts carry a 5%–15% rolling reserve held for 180 days to soften the elevated dispute risk on card-funded send and prepaid load transactions (which settle into beneficiary accounts or onto reloadable cards within minutes of card authorization and become irreversible from the merchant side). Established licensed money transmitters with clean processing history, full FinCEN Form 107 currency, and comprehensive state MTL coverage can qualify for reserves at the 5% end. New MSB operators, cross-border remittance corridor operators, crypto-as-MSB exchanges, and offshore-placed MSBs typically sit toward the 15% end. Reserve percentages can be renegotiated downward after 6–12 months of clean MSB processing.

An MSB business is classified as the highest-compliance-burden vertical in payments because its MCC (6051 for financial institutions / quasi-cash, 6012 for financial institutions / merchandise, 6211 for security brokers) is on every card brand's restricted MCC list, because card-funded send and prepaid load transactions carry elevated chargeback exposure tied to the irreversibility of corridor settlement and stolen-card monetization through MSB rails, because the regulatory landscape (FinCEN Form 107, state-by-state MTL across ~49 states, BSA/AML, OFAC SDN, FATF Travel Rule, USA PATRIOT Act CIP, CTR/SAR filing, NY BitLicense for crypto-as-MSB) is the most extensive of any commercial vertical, and because sanctions exposure on cross-border corridors creates ongoing AML risk that the acquirer underwrites continuously.

Yes. 2Accept underwrites licensed money transmitters operating US-to-LatAm, US-to-Africa, US-to-Asia, and US-to-Europe remittance corridors with full FinCEN Form 107 registration current, comprehensive state MTL coverage (typically 30–49 states for nationwide remittance corridors), FATF Travel Rule integration on transfers above $3,000 under Rule 16, OFAC SDN screening on every send and every beneficiary, and corridor-specific compliance review. Cross-border remittance MIDs are typically priced interchange-plus with multi-currency settlement in the destination corridor currency.

Yes. Prepaid card issuers (open-loop reloadable cards under bank sponsorship via Marqeta, Galileo, i2c, or Stripe Treasury) and payroll card issuers qualify under MCC 6051 (open-loop) or MCC 6012 (closed-loop) with full FinCEN Form 107 registration, state-by-state MTL where required, BSA/AML program with designated Compliance Officer, OFAC SDN screening on every load, and CTR filing on cash-equivalent loads above $10,000. Both employer-funded payroll card reload and consumer-funded prepaid reload are supported, with FSA/HSA compatibility on healthcare-specific cards.

Yes. Agent-network MSB operators (principal MSB authorizing independent retail agents to originate transactions under the principal's FinCEN registration) qualify with documented agent agreements, supervised compliance, and OFAC screening enforced at the agent level. Fintech MSBs operating under bank sponsorship (sponsor bank handles final settlement, fintech handles consumer-facing UI plus KYC, AML, and Travel Rule layer) qualify with a sponsor bank letter, documented operating agreement allocating BSA/AML responsibility, and a sponsor bank's BSA officer attestation that the fintech MSB is supervised under the bank's overall AML program.

Yes. 2Accept holds acquiring relationships with banks in the United States, United Kingdom, European Union, Caribbean, and APAC regions that approve licensed money transmitters, prepaid card issuers, FX businesses, P2P platforms, crypto-as-MSB exchanges, and remittance corridor operators. Non-U.S. MSB operators open accounts with multi-currency settlement in USD, EUR, GBP, CAD, AUD, MXN, and JPY. Offshore placement is typical for operators serving cross-border remittance corridors (US-to-LatAm via MXN, US-to-Europe via EUR/GBP), operators in early-stage state MTL coverage, and operators serving sanctions-sensitive jurisdictions with elevated compliance overhead.

Yes. 2Accept underwrites crypto exchanges and custodial wallet operators registered as MSBs under FinCEN Form 107 covering both crypto exchange and fiat custody activity. Crypto-as-MSB requires full state MTL coverage where required, New York BitLicense if serving NY residents (a separate multi-million-dollar licensing track with NY DFS), Chainalysis KYT or equivalent chain-analysis on every deposit and withdrawal address, FATF Travel Rule on outbound crypto transfers above $3,000 under Rule 16, OFAC SDN screening on every cardholder and every counterparty wallet, and BSA/AML written program with designated Compliance Officer.

Yes. P2P payment platforms running Venmo-style closed-loop transfer networks qualify under MCC 6051 with FinCEN Form 107 registration, state-by-state MTL coverage (typically required in all states with money transmitter statutes), tiered KYC (Tier 1 / Tier 2 / Tier 3 limits), OFAC SDN screening on every transfer (sender, receiver, and both bank counterparties), FATF Travel Rule on outbound transfers above $3,000 under Rule 16, and continuous transaction monitoring via ComplyAdvantage with rule-based SAR triggers.

Yes. 2Accept can consider MATCH-listed MSB applicants. Full disclosure of the termination reason code is required (reason code 04 — Excessive Chargebacks, reason code 12 — Fraud Conviction, reason code 14 — Money Laundering, etc.) along with a remediation plan addressing the underlying cause. MATCH-listed MSB merchants are typically placed on offshore acquirers with enhanced rolling reserve (15%–25%) for the first 6 months and the option to migrate domestic after clean processing history establishes and FinCEN/state MTL compliance posture is audit-verified.

Clean MSB processing history (chargeback ratio under 0.5%, zero OFAC hits over the prior 12 months, on-time CTR/SAR filings), six or more months of bank statements showing consistent MSB fee revenue, current FinCEN Form 107 registration with renewal more than 60 days out, comprehensive state MTL coverage (or geofencing on non-licensed states), a documented BSA/AML written program with a CAMS-certified Compliance Officer, live FATF Travel Rule integration via Sumsub Travel Rule or Notabene, real-time OFAC SDN screening via ComplyAdvantage or Refinitiv World-Check on every transaction, KYC stack via Sumsub or Onfido with tiered limits enforced, and (if crypto-as-MSB) Chainalysis KYT running on every deposit and withdrawal address all strengthen approval.

Yes. New MSB businesses without prior processing can be considered at mid- to top-tier pricing with a 10–15% rolling reserve and personal guarantee. Projected MSB volume, KYC tier structure quality, compliance posture (FinCEN Form 107 current, state MTL in target customer states, BSA/AML written program live, OFAC SDN screening live, FATF Travel Rule integration live, CTR/SAR workflow audited), business plan, principal experience in regulated finance or fintech, and the Sumsub + Onfido + Chainalysis + Refinitiv + ComplyAdvantage stack you have integrated all substitute for processing history. The reserve drops after 90–180 days of clean MSB processing.

If a primary acquirer denies your MSB application, 2Accept automatically reshops it to secondary and offshore MSB-friendly banks within our network — including FinCEN-aware acquirers in the U.K., EU, Caribbean, and APAC — without requiring you to resubmit. If all placements decline, you receive a written explanation and a remediation roadmap specific to MSB underwriting (e.g., renew Form 107 before resubmission, expand state MTL coverage to specific customer-resident states, integrate FATF Travel Rule via Sumsub or Notabene, switch OFAC screening providers, pursue New York BitLicense for NY-facing crypto-as-MSB operations, or restructure beneficial ownership to clear an OFAC near-match).

A soft credit inquiry is run during MSB underwriting for personal guarantee verification on the principal signer and 25%+ beneficial owners under CDD rules. Soft pulls do not affect your FICO score and do not appear on your credit report to other lenders. Hard credit pulls can be used in some cases depending on the particular acquiring bank's requirements — typically only for offshore-placed MSB accounts with elevated rolling reserves where the principal's personal solvency materially affects the acquirer's risk model.

First-pass MSB rejections usually result from expired or missing FinCEN Form 107 registration, severe state MTL gaps in customer-resident states without geofencing remediation, missing New York BitLicense on crypto-as-MSB applicants serving NY residents, an outdated or undocumented BSA/AML written program, missing designated Compliance Officer, no FATF Travel Rule integration on transfers above $3,000, absent OFAC SDN screening on transactions (not just customers), no CTR/SAR filing workflow audit trail, no Chainalysis KYT on crypto-as-MSB deposits and withdrawals, MCC-to-service mismatch (running open-loop prepaid issuer flow under a closed-loop MCC), a disclosed chargeback ratio above 1.5%, prior FinCEN enforcement action, or the applicant's principal appearing on an OFAC near-match list. 2Accept's MSB underwriter catches most of these before submission to prevent rejections.

Approximately 95% of MSB merchants who complete a full application with all required documentation (FinCEN Form 107 current, state MTL coverage map, BSA/AML written program with designated Compliance Officer, OFAC SDN screening provider live, FATF Travel Rule integration live, KYC stack configured via Sumsub or Onfido, CTR/SAR filing workflow audited, Chainalysis KYT if crypto-as-MSB, NY BitLicense if applicable) get approved. The ~5% rejection rate is driven by OFAC sanctions matches on the principal or beneficial owners, active FinCEN enforcement action, expired or missing Form 107, severe state MTL gaps in target customer states, missing BitLicense for NY-facing crypto-as-MSB operators, or the applicant being on the card brand's internal MSB fraud watchlist.

3DS 2.0 is mandatory on every card-funded send and prepaid load transaction under card-network MSB programs and shifts liability for fraud-based chargebacks (reason codes 10.4, 83) from the merchant to the issuing bank on authenticated MSB transactions. It does not eliminate friendly fraud, product-not-received disputes (where the customer claims the remittance never arrived at the beneficiary), or buyer's-remorse disputes (where the exchange rate moves against the sender post-send). Implementing 3DS typically reduces total MSB chargebacks by 40%–60% and saves $8–$15 per transaction in fraud losses on the higher average tickets common to MSB activity.

VAMP — Visa Acquirer Monitoring Program — is Visa's expanded chargeback and fraud monitoring framework launched as the successor to VDMP and VFMP. On MCC 6051 MSB MIDs, VAMP applies stricter ratio thresholds (Early Warning around 0.65%, formal enrollment around 0.9%) than the standard 0.9%/1.0% framework that applies to other verticals. VAMP enrollment imposes escalating fines ($5,000–$50,000 monthly), mandatory chargeback reduction plans, additional Visa MSB program scrutiny including OFAC and Travel Rule compliance audit, and a path to permanent MATCH listing if the MSB ratio is not remediated within 6 months.

Yes. 2Accept's representment team files compelling-evidence packages on MSB disputes (signed terms-of-service acceptance, KYC attestation with biometric match timestamp via Sumsub or Onfido, IP logs at the moment of transaction, AVS and CVV match, OFAC SDN screening pass record, Travel Rule data exchange log if above $3,000, beneficiary receipt confirmation, and corridor settlement reference) to win friendly fraud cases at roughly 50%+ for 2Accept-managed MSB disputes. MSB win rates run slightly lower than standard e-commerce because issuing banks favor cardholders on irreversible corridor settlements, but compelling evidence with KYC biometric proof and beneficiary receipt confirmation still wins majority of cases.

A refund is initiated by the merchant (in response to an Ethoca/Verifi alert or a direct customer request) and returns fiat funds to the customer without a dispute entry on the MSB MID. A chargeback is initiated by the customer through their issuing bank, carries a reason code (10.1–13.9 for Visa), counts against the VAMP and ECM ratios, and imposes a $25–$50 chargeback fee regardless of outcome. Refund-before-chargeback via Ethoca + Verifi is the core prevention strategy on MSB MIDs because the underlying corridor settlement or prepaid load cannot be reversed.

A Visa representment cycle on MSB disputes resolves in 45–60 days: merchant submits evidence (30 days), issuer reviews (30 days), and the final case status posts in the merchant portal. Mastercard cycles run 45 days. Amex resolves in 20 days. Winning representments recover both the MSB transaction amount and the chargeback fee — but unlike retail e-commerce, the underlying corridor settlement, prepaid load, or P2P transfer is already irreversible from the merchant side, so a lost representment means the merchant absorbs both the fiat-side loss and the corridor-leg cost.

Verifi CDRN is owned by Visa and covers Visa issuers — particularly important on MSB because Visa's MSB-specific chargeback programs run through Verifi's infrastructure for the dispute-handling tier. Ethoca is owned by Mastercard and covers Mastercard plus Amex, Discover, and some Visa issuers. Using both networks together covers roughly 90% of U.S. card-issuing banks — essential on MSB MIDs where dispute volume on card-funded send and prepaid load transactions is structurally elevated due to corridor irreversibility and stolen-card monetization.

Visa's VAMP (Visa Acquirer Monitoring Program) thresholds on MCC 6051 are stricter than standard e-commerce — sustained ratios above 0.65% trigger Early Warning, and crossing 0.9% leads to formal enrollment. Mastercard's ECM threshold is 1.5% but with stricter scrutiny on MSB MIDs. Staying over either threshold for 4+ months leads to enrollment in VAMP, ECM, or VFMP, additional fines of $25,000–$200,000, and possible MSB MID termination with MATCH listing under reason code 04 (Excessive Chargebacks). MSB operators target sub-0.5% ratios as a working buffer.

Stripe, Square, and PayPal are payment aggregators that pool thousands of merchants under one master MID and explicitly prohibit MSB activity — money transmission, prepaid card issuance, money orders, FX, P2P transfer platforms, and crypto-as-MSB — in their acceptable-use policies. Even MSB accounts they initially approve (often by misclassification at sign-up before a descriptor surfaces "money transmitter," "remittance," or "prepaid load") get frozen the moment the aggregator's automated screening triggers. 2Accept issues a dedicated MSB MID from a FinCEN-aware acquiring bank that explicitly approves MCC 6051, MCC 6012, and MCC 6211 flows, so the account cannot be shut down for doing the MSB business it was approved to serve unless there is a change in laws, regulations, or card brand MSB program rules.

Marqeta, Galileo, and i2c are prepaid card issuer-processors that issue cards under sponsor bank arrangements — they handle the card-issuance side of the prepaid program but do not provide the consumer-facing card-acquiring (the layer where end-customers fund their prepaid balance with a debit or credit card). 2Accept provides the complementary card-acquiring MID that lets prepaid card holders fund their balance with Visa, Mastercard, Amex, and Discover, with full BSA/AML, OFAC SDN screening, and CTR filing on every load. Many prepaid issuer programs run Marqeta or Galileo on the issuance side with 2Accept on the funding-acquiring side.

Yes. If you currently use Authorize.net, NMI, USAePay, or any compatible gateway for your MSB card-funded send, prepaid load, or FX exchange flow, 2Accept switches only the acquiring bank behind it. Your MSB checkout flow, customer KYC vault, biometric attestation logs, Travel Rule integration, OFAC SDN screening provider, CTR/SAR filing workflow, and chain-analysis tooling (if crypto-as-MSB) remain in place with no customer-visible change and no re-integration work on the front end — only the underlying MID and settlement bank change.

Yes. 2Accept offers native integration with the five compliance providers MSB operators standardize on: Sumsub for end-to-end KYC, AML screening, and FATF Travel Rule data exchange under Rule 16; Onfido for ID verification, biometric face match, and document authenticity; Chainalysis KYT for crypto-side chain analytics on crypto-as-MSB operators and remittance corridors with crypto settlement legs; Refinitiv World-Check for PEP and adverse media screening; and ComplyAdvantage for real-time transaction monitoring with rule-based SAR triggers. Integration is configured at underwriting and runs on every transaction at the acquirer layer.

Yes. Running a primary and backup MSB processor (or multi-MID load balancing across 2–5 MSB accounts) is standard risk practice for high-volume MSB operators. 2Accept builds multi-MID structures into Mid-Tier and Top-Tier MSB plans by default — for example, separate MIDs for remittance corridor flow, prepaid issuer load, P2P transfer funding, FX exchange, and crypto-as-MSB activity, each independently monitored against VAMP and ECM thresholds and each with its own FinCEN, state MTL, BSA/AML, OFAC, and Travel Rule compliance audit trail.

Authorize.net and NMI are payment gateways, not merchant accounts. A gateway transmits card-funded send card data between your MSB platform UI and the acquiring bank but does not underwrite or settle MSB-related fiat funds, nor does it provide BSA/AML, OFAC SDN screening, FATF Travel Rule, or CTR/SAR filing workflow. You still need a dedicated MSB merchant account behind them. 2Accept supports direct integration with both Authorize.net and NMI as gateway pass-throughs, while many MSB operators run our native 2Accept gateway with direct REST API support for remittance corridor engines and prepaid issuer platforms.

PaymentCloud, Durango, and Soar are ISOs/MSPs similar to 2Accept, but they operate primarily as resellers with variable pricing and do not specialize in MSB underwriting. They typically refer MSB applications to a single offshore partner without state-by-state MTL guidance, FATF Travel Rule integration support, or BitLicense advisory for crypto-as-MSB applicants. 2Accept publishes flat-tier pricing upfront on the lower-risk MSB tiers, includes chargeback alerts in standard plans, provides dedicated MSB underwriters who understand FinCEN Form 107, the 49-state MTL patchwork (Montana excluded), BSA/AML, OFAC SDN screening, FATF Travel Rule Rule 16, CTR/SAR filing, and NY BitLicense, integrates natively with Sumsub, Onfido, Chainalysis KYT, Refinitiv World-Check, and ComplyAdvantage on the acquirer side, and offers approvals on the spectrum from established licensed money transmitters to agent-network operators to crypto-as-MSB exchanges.