LPM LocalPayMapLocal payment directory

Contacts

PSP contacts directory

Filter public PSP, gateway, acquirer, aggregator, wallet, and mobile-money contact routes by market, provider type, and contact status.

1391Contact recordsPublic feed
523Public emailConservative labels
384Form onlyOfficial routes
7Current resultsAfter filters

Contact workflow

Current filter: open banking

Treat contacts as a verification queue, not final recommendations. Confirm entity, industry, local-company requirements, settlement, refunds, disputes, pricing, and launch support one by one.

7results 4public email 2official form 1official page

A public email is not automatically a sales email; generic and support inboxes stay labelled as general contact routes. If no email is available, use the official form or page first.

Submit requirementsAsk on WhatsApp

Provider types

Filter by provider role

Start by separating PSPs, acquirers, wallets, gateways, networks, and bank merchant-services routes, then verify entity, category, pricing, and settlement with official providers.

Payment gatewaySome gateways are bundled with PSP or acquiring services, while others connect to separate banks, acquirers, wallets, and processors. Merchants should identify the contract party, funds-flow owner, method owner, and support path before treating a gateway as a full payment provider.PSP / aggregatorThe merchant usually contacts the PSP or aggregator directly, but the provider may rely on underlying acquirers, banks, schemes, wallets, or local processors. Ask who contracts, who settles, which methods are enabled for this merchant, and which routes need additional review or documents.Acquirer / merchant servicesA merchant may contract directly with an acquirer, use acquiring through a PSP or payment facilitator, or reach it through an ecommerce platform. Ask whether the named provider is the acquirer, processor, gateway, or reseller, and whether scheme, wallet, refund, dispute, and settlement roles are split.Wallet operatorSome wallets offer direct merchant onboarding, while others rely on PSPs, gateways, acquirers, marketplaces, QR aggregators, or local partners. Ask whether the wallet operator is the contract party, whether another provider processes the transaction, and which support path applies.Mobile money operatorMerchants may connect through the operator, a mobile-money aggregator, PSP, gateway, bank, marketplace, or local partner. The practical route can differ by country and operator, so confirm whether the merchant is dealing with the operator directly or through a technical and commercial intermediary.Bank merchant servicesThe route can be direct with a bank merchant-services team, or indirect through a PSP, gateway, platform, or local integrator that uses a bank behind the scenes. Merchants should ask who contracts, who settles funds, who supplies the integration layer, and which payment products are actually in scope.Card network / switchMost merchants do not onboard only through the scheme brand. They usually connect through an acquirer, bank, PSP, payment facilitator, gateway, wallet operator, or platform. Ask which scheme is used, who sponsors acceptance, and which party owns settlement, disputes, and operating support.BNPL providerMerchants may contract directly with a BNPL provider or access the option through a PSP, gateway, ecommerce platform, marketplace, or wallet. Confirm whether the BNPL company underwrites shoppers directly, whether the PSP only routes checkout, and which markets or categories are available.Payout / remittanceThe route may be a payout API, remittance platform, bank transfer provider, wallet payout partner, payroll tool, or PSP module. Merchants should confirm whether funds originate from collected payments, prefunded balances, bank accounts, or treasury wallets, and who manages compliance checks.Open banking / pay by bankAccess may come from a regulated open-banking provider, a bank, a PSP, a gateway, or a local account-to-account rail partner. Merchants should verify whether the provider initiates payments, only reads account data, packages bank transfers, or simply routes to another participant.Payment providerPayment-related provider that needs manual classification.

Merchant usage and connection route

Open banking / pay by bank in the payment stack

Open banking and pay-by-bank routes are relevant when a merchant wants account-to-account checkout, bank redirect, payment initiation, virtual account, direct debit, or similar bank-funded flows. Use this category to test conversion, confirmation, refund, reconciliation, and customer support implications.

Connection route

Access may come from a regulated open-banking provider, a bank, a PSP, a gateway, or a local account-to-account rail partner. Merchants should verify whether the provider initiates payments, only reads account data, packages bank transfers, or simply routes to another participant.

Verification questions

  • Is the flow payment initiation, bank redirect, virtual account, direct debit, QR, request-to-pay, or manual bank transfer?
  • Which banks, countries, currencies, shopper authentication steps, and device flows are actually covered?
  • Who provides payment confirmation, failed-payment states, refund handling, and reconciliation identifiers?
  • What consent, data access, compliance, and customer support responsibilities fall on the merchant?
  • Does the provider hold funds, initiate transfers, or only pass instructions to another party?

Merchant caveats

  • Bank participation and shopper experience can differ by country and provider.
  • Instant authorization messages should not be treated as confirmed merchant settlement.
  • Open-banking data access is not the same as payment collection.
  • Refunds and disputes may not mirror card workflows.

Provider examples to verify

BrankasAFS Open BankingPayNow providersSPEI providers

Related markets

Global

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Generic inboxes are not treated as sales emailsForm-only entries keep official routes and WhatsApp fallback

Bahrain · Open banking / pay by bank · Public email

AFS Open Banking

Open banking APIsPISPAISPBank transfers

Bahrain Open Banking API route from Arab Financial Services for payment initiation and account information use cases.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

Email general inboxOfficial site
Nigeria · Open banking / pay by bank · Public email

ADAMMA

payment initiationvirtual accountsidentity verificationopen banking APIs

ADAMMA offers open banking APIs, payment initiation, virtual accounts and developer sandbox access for Nigerian financial products.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

Email business intakeOfficial site
Qatar · Open banking / pay by bank · Public email

Olive PayTech

QFC-licensed Qatar fintech infrastructure provider enabling payment initiation APIs for merchant and fintech payment flows.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

Email general inboxOfficial site
Rwanda · Open banking / pay by bank · Public email

BK Open API

BK paymentscollectionspayoutsopen API

Rwanda fintechs, marketplaces, billers and enterprise platforms needing permissioned bank API payments.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

Email general inboxOfficial site
Saudi Arabia · Open banking / pay by bank · Official form only

Lean Technologies

account-to-account paymentsopen bankingbank datapayout support

Best for fintechs and platforms needing Saudi open-banking payments or bank connectivity rather than card acquiring.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Open official formOfficial site
United States · Open banking / pay by bank · Official form only

Dwolla

ACHsame day ACHRTPwire transfers

U.S. bank-payment infrastructure platform for ACH, real-time payments, wires, and embedded money movement.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

No public sales email found yet. Open official form or ask LocalPayMap to help verify.

Open official contact formOfficial site
Bolivia · Open banking / pay by bank · Official page only

Banco Nacional de Bolivia Open Banking

QR Simple APIQR Simple by third partiesDirect debitTreasury APIs

Bank API route for Bolivia business clients; confirm account, contract and API credentials with BNB.

Role to verify: Verify whether this lead is the contracting provider, technical integrator, wallet operator, bank route, acquirer, or platform route.

No public sales email or explicit form found yet. Open the official page or ask LocalPayMap to help verify.

Open official contact pageOfficial site