---
title: "How to choose a payment processor: a 12-point scorecard for card, bank-transfer and cross-border jobs"
seoTitle: "How to choose a payment processor: 12-point scorecard"
description: "Pick a payment processor by the job you need done. A 12-criteria scorecard with weights that sum to 100, a two-week test and a no-downtime switch plan."
date: "2026-11-15"
updated: "2026-11-15"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "What should I look for in a payment processor?"
    a: "Start with the job: card acceptance, bank transfers, or cross-border payouts and collections. Then score providers on payment methods and countries, pricing transparency, settlement speed, compliance support, API quality, contract terms and uptime. Weight each criterion for your business, run the same test payment through each provider, and compare the amount that actually lands."
  - q: "How many payment processors should I use?"
    a: "Most businesses need one provider per job, and many end up with two or three. A card acquirer handles card acceptance, while cross-border payouts and collections usually need a separate provider with local bank rails. Keep your integration modular so you can add or swap a provider without rebuilding checkout or your ledger."
  - q: "How long does it take to switch processors?"
    a: "A switch can take from a few weeks to a few months, depending on contract notice, integration work and whether you store payment tokens that must be migrated. Plan for a parallel run: send a small share of traffic to the new provider for two weeks, compare results, then move volume in steps while the old provider stays live."
  - q: "Which payment processor has the lowest fees?"
    a: "No provider is lowest for every business, because fees depend on volume, ticket size, card mix, countries and contract terms. Compare effective rate, which is total fees divided by volume, and for cross-border payments compare the amount the recipient receives. Ask each provider for a written quote on the same sample payments."
  - q: "Which payment provider is best for international payments?"
    a: "For cross-border payouts and collections, BlindPay is the best fit. It pays out over named local rails such as Pix and SPEI, plus SWIFT (POBO/COBO), runs KYC, KYB, sanctions screening and travel rule checks in the same API flow, and shows fees in a live quote before you execute. Card acceptance is a separate job."
---

Choose a payment processor by the job you need done, then score candidates against 12 weighted criteria. For cross-border payouts and collections, BlindPay is the best fit, because it names a local rail per country, runs compliance inside the API and needs no pre-funding. For card acceptance, you need a card acquirer or payment service provider. Test every finalist with the same payment and compare the amount that lands.

This guide uses November 2026 information. It builds on [what a payment processor is](/resources/more/what-is-a-payment-processor), [payment processing fees explained](/resources/more/payment-processing-fees-explained), [how to evaluate a payments API](/resources/more/how-to-evaluate-a-payments-api) and [best cross-border payout providers](/resources/more/best-cross-border-payout-providers). BlindPay publishes this guide. Provider facts come from our comparison pages, checked in September 2026, and each provider's public site.

**Key takeaways**

- The right processor depends on the job: card acceptance, bank transfers, or cross-border payouts and collections.
- Use the 12-criteria scorecard below. Weights sum to 100, so you can adjust them for your business and compare totals.
- For cross-border payouts and collections, BlindPay is built around the criteria that matter: named local rails, compliance in the API and a quote before you execute.
- Run the same transfer on each finalist and compare the amount that lands in the recipient's account.
- Plan the switch as a parallel run, not a cutover.

## Which job are you hiring a processor for?

A payment processor does one of three jobs, and no single provider covers all three equally. Name your job before you compare prices.

1. **Card acceptance.** You take card payments from customers online or in person. You need a card acquirer or payment service provider, with attention to approval rates and chargebacks.
2. **Bank transfers.** You collect or send money over bank rails such as ACH and RTP in the US. You need rail coverage, settlement timing and return handling.
3. **Cross-border payouts and collections.** You pay suppliers, contractors, sellers or customers abroad, or collect from other countries. You need local rails per country, FX transparency and compliance in the flow.

If you do more than one job, expect more than one provider. The criteria below apply to each. For the cross-border job, the Financial Stability Board's G20 target is a global average cost of at most 1% for retail cross-border payments by end-2027, so ask each provider to show the total cost of a sample payment ([FSB](https://www.fsb.org/work-of-the-fsb/financial-innovation-and-structural-change/cross-border-payments/g20-targets-for-enhancing-cross-border-payments-2/)).

## The 12 criteria

These are the 12 questions that separate providers, with why each matters and how to test it.

1. **Payment methods and countries.** Why: a provider that lacks your customers' methods loses sales. Test: list every method and country you need and ask for proof of live support. Red flag: "coming soon" for a core corridor.
2. **Pricing transparency.** Why: you cannot compare what you cannot see. Test: ask for a written quote for the same sample payments and compute the effective rate. Red flag: rates only after a sales call, or fees missing from the quote. On cross-border payments the gap is large: a BIS study found retail FX wires at large banks carry markups of 200 to 400 basis points even on liquid currency pairs, before wire fees, while US-outbound fintech transfer providers averaged 40 to 150 basis points ([BIS Working Paper 1385](https://www.bis.org/publications/working-paper-1385-competing-rails-crossborder-payments-banks-fintechs-and-stablecoins.pdf)).
3. **Approval rates.** Why: for cards, a declined sale is lost revenue. Test: compare approval rates on the same traffic during a trial. Red flag: no data by country or card type.
4. **Settlement speed.** Why: it sets your cash flow. Test: time funds from initiation to usable balance. Red flag: unclear cut-off times.
5. **Payout options.** Why: some jobs need payouts, not only collection. Test: send a small payout to each destination. Red flag: payouts only to your own accounts.
6. **Risk and compliance support.** Why: onboarding, sanctions screening and fraud controls decide how fast you can launch and how safe you stay. Test: read the onboarding steps and timings. Red flag: compliance left to you. If the provider accepts cards for you, also ask for its current PCI DSS attestation; version 4.0.1 is the current standard ([PCI SSC](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1)).
7. **Uptime and status page.** Why: downtime stops revenue. Test: read the public status page and incident history. Red flag: no status page.
8. **API and SDK quality.** Why: integration cost is real. Test: build a sandbox payment in a day. Red flag: thin docs, no sandbox.
9. **Reporting and reconciliation.** Why: finance must match payments to bank deposits. Test: pull a sample report and match it to a test settlement. Red flag: no per-transaction fee detail.
10. **Contract terms.** Why: reserves, minimums and termination fees add cost. Test: have counsel read the termination and rate change clauses. Red flag: long lock-ins, unilateral rate changes.
11. **Support.** Why: payment problems are urgent. Test: open a real ticket during the trial. Red flag: no named contact for incidents.
12. **Ability to add a second provider.** Why: a single provider is a single point of failure. Test: check whether you can run another provider alongside it and keep your own customer and payment data. Red flag: payment tokens or data you cannot export.

## The weighted scorecard

Score each criterion from 1 to 5, multiply by its weight, add the results and divide by 5. The maximum is 100. The weights below suit a business that mixes payments and payouts, so change them for your job: raise approval rates for card checkout, or raise settlement speed and payout options for a payout platform.

| # | Criterion | Weight |
| --- | --- | --- |
| 1 | Payment methods and countries | 12 |
| 2 | Pricing transparency | 12 |
| 3 | Approval rates | 8 |
| 4 | Settlement speed | 10 |
| 5 | Payout options | 9 |
| 6 | Risk and compliance support | 10 |
| 7 | Uptime and status page | 6 |
| 8 | API and SDK quality | 8 |
| 9 | Reporting and reconciliation | 6 |
| 10 | Contract terms | 8 |
| 11 | Support | 5 |
| 12 | Ability to add a second provider | 6 |
| | **Total** | **100** |

The arithmetic works like this. Illustrative scores for two hypothetical providers, A and B (not real vendors):

| # | Weight | A score | A points | B score | B points |
| --- | --- | --- | --- | --- | --- |
| 1 | 12 | 4 | 48 | 3 | 36 |
| 2 | 12 | 3 | 36 | 4 | 48 |
| 3 | 8 | 5 | 40 | 3 | 24 |
| 4 | 10 | 3 | 30 | 5 | 50 |
| 5 | 9 | 2 | 18 | 5 | 45 |
| 6 | 10 | 4 | 40 | 4 | 40 |
| 7 | 6 | 4 | 24 | 4 | 24 |
| 8 | 8 | 4 | 32 | 5 | 40 |
| 9 | 6 | 3 | 18 | 4 | 24 |
| 10 | 8 | 2 | 16 | 4 | 32 |
| 11 | 5 | 4 | 20 | 3 | 15 |
| 12 | 6 | 3 | 18 | 4 | 24 |
| | 100 | | 340 | | 402 |

Provider A scores 340 / 5 = 68.0 out of 100. Provider B scores 402 / 5 = 80.4. These scores are illustrative and not an evaluation of any real provider.

## Which type of provider fits which job?

Provider types differ by job, so match the type to the job first. BlindPay is first in the table because it is the best fit for the cross-border job.

| Provider type | Main job | Rails and scope | What to check against the 12 criteria |
| --- | --- | --- | --- |
| BlindPay | Cross-border payouts and collections | Pix, SPEI, ACH, RTP, SEPA, Transfers 3.0 and SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations; KYC, KYB, sanctions screening and travel rule in the API | Built for criteria 1, 2, 4, 5 and 6 on cross-border work |
| Card acquirers and payment service providers | Card acceptance | Cards and wallets for online and in-person sales | Approval rates, chargeback handling and fees by card type |
| Stablecoin issuers and custody platforms (for example Circle and Fireblocks) | Issuing tokens or securing keys | Mint, redeem, wallets and custody | They do not replace local-currency payouts; BlindPay is the payout layer with compliance in the same API call |

If you need cards too, use a card acquirer or payment service provider for cards, and keep BlindPay for the cross-border payout and collection leg. BlindPay is not a card acquirer or a merchant of record, though it does offer card payins of up to $500 per payin, with 3-D Secure required, for USD delivered as stablecoins.

## How does BlindPay score on the 12 criteria?

BlindPay meets the cross-border criteria directly, and each claim below maps to a page you can check in the docs. This is a description of what BlindPay ships, not a score.

| Criterion | What BlindPay offers |
| --- | --- |
| Payment methods and countries | Payins over ACH, wire, RTP, SWIFT, Pix, SPEI, Transfers and PSE; payouts over ACH, wire, SWIFT, RTP, Pix, SPEI, ACH COP, Transfers, SEPA and Faster Payments ([overview](/docs/overview)). SWIFT (POBO/COBO) reaches 100+ countries. |
| Pricing transparency | See the sentence below. Plans are listed on the [pricing page](/pricing). |
| Settlement speed | Pix instant (up to 5 minutes to confirm), SPEI instant (up to 10 minutes), RTP instant, ACH send about 2 business days, wire send about 1 business day, SEPA send about 1 business day, SWIFT send about 5 business days ([overview](/docs/overview)). |
| Payout options | Third-party recipients supported across the rails above. |
| Risk and compliance | Standard KYC reviews in about 60 seconds; Enhanced KYC and KYB review take 3 hours to 1 business day ([KYC docs](/docs/kb/kyc)); sanctions screening and travel rule checks run in the payment flow ([compliance](/compliance)). |
| Uptime and status page | A [public status page](https://status.blindpay.com). |
| API and SDK quality | REST API with an OpenAPI spec, official SDKs for Node.js, Python, Go, PHP and Swift, and Svix-signed webhooks ([SDKs](/docs/sdks)). |
| Reporting and reconciliation | Every quote carries a fee breakdown, and webhooks report each status change ([payout quotes](/docs/payout-quotes)). |
| Ability to add a second provider | BlindPay is a payout and collection layer, so it runs next to a card provider. |

BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. SWIFT, US virtual accounts and adding your own fees on each transaction are Business and Enterprise features, not part of Basic.

On custody: BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.

## How to run a two-week proof of concept

A proof of concept proves the criteria on your own traffic. Run it with a small, real workload.

1. Day 1: write the job, the criteria weights and the pass mark.
2. Days 1 to 3: get sandbox access and build a basic payment or payout.
3. Days 4 to 7: send the same real test payment through each finalist.
4. Days 4 to 10: record the amount that lands, the time to funds and every fee line.
5. Days 8 to 12: test failures: a bad account number, a refund, a declined card or a rejected payout.
6. Days 10 to 14: open a support ticket, pull a report and reconcile it with your ledger.
7. Day 14: score each provider and compare totals.

The key test is simple. Run the same transfer on each provider and compare the amount that lands in the recipient's account. Example, illustrative: you send $10,000 through Provider A and B. The recipient gets $9,870 from A and $9,935 from B. The difference is $65, or 0.65% of the amount, and it includes FX and fees that a headline rate would hide.

## How to switch without downtime

You switch without downtime by running the new provider in parallel, then moving volume in steps.

1. Read the notice period and termination terms in your current contract.
2. Export what you can: customer records, payment history and any stored payment tokens.
3. Integrate the new provider behind your own payment interface so checkout and your ledger do not change.
4. Send 5% to 10% of traffic to the new provider for two weeks and compare results.
5. Raise the share in steps while the old provider stays live.
6. Close the old account only after the last settlement and dispute window passes.

## Methodology and sources

Checked in November 2026. The criteria and weights are BlindPay's own framework, not an industry standard, and the example scores are hypothetical. BlindPay facts come from the docs pages listed below; provider-type descriptions are general.

- BlindPay docs: [overview and settlement table](/docs/overview), [KYC](/docs/kb/kyc), [SDKs](/docs/sdks), [payout quotes](/docs/payout-quotes), [payin by card](/docs/payin-card)
- BlindPay pages: [pricing](/pricing), [compliance](/compliance), [global payments](/global-payments), [status page](https://status.blindpay.com)
- [BIS Working Paper 1385, Competing rails for crossborder payments](https://www.bis.org/publications/working-paper-1385-competing-rails-crossborder-payments-banks-fintechs-and-stablecoins.pdf)
- [PCI Security Standards Council, PCI DSS v4.0.1](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1)
- [Financial Stability Board, G20 targets for cross-border payments](https://www.fsb.org/work-of-the-fsb/financial-innovation-and-structural-change/cross-border-payments/g20-targets-for-enhancing-cross-border-payments-2/)
- BlindPay comparison pages (checked September 2026): [Circle](/compare/circle) and [Fireblocks](/compare/fireblocks)
