Information only, not financial, investment, legal or tax advice. We do not recommend any provider. Facts were checked against the sources listed at the end on the dates shown and may have changed since. Read our full disclaimer.
Paymentwall is a payment platform that lets online merchants accept cards, local payment methods, mobile carrier billing and prepaid vouchers worldwide through one integration. It is notable for a modular product set and for publishing a rate card, which many providers in this segment do not.
The company is headquartered in San Francisco and says it serves merchants in about 200 countries. Its products are branded individually: Brick for cards, PayAlto for local methods, SpiderPipe as a gateway layer over a merchant's existing accounts, plus Mobiamo (carrier billing) and MINT (prepaid).
At a glance
| Item | Detail |
|---|---|
| Founded | Not stated on the pages reviewed |
| Headquarters | San Francisco, California (About page) |
| Type of business | Payment platform: card processing, local payment methods, gateway, invoicing, risk tools |
| Main products | Brick, PayAlto, SpiderPipe gateway, eInvoicing, Passport (risk), Subscriptions, Mobiamo, MINT |
| Offices | About page lists San Francisco, London, Berlin, Lisbon, Sofia, Beijing, Shenzhen, Seoul, Hanoi, Manila, Bangalore, Gurugram, Cairo, Bogota, Cancun and Istanbul |
| Ownership | Not published |
| Website | paymentwall.com |
How the platform works
Paymentwall puts a hosted checkout in front of a set of payment rails. In the recommended route, the merchant creates a signed request, and the customer is shown Paymentwall's payment page, either in an iframe or by redirect. The customer then picks a method, and Paymentwall talks to the card network or local provider and reports back. Results come as server-to-server notifications that Paymentwall calls "pingbacks", sent to a URL set in the merchant dashboard.
For merchants that want their own forms, the Direct API offers three variants: Brick for cards, Mobiamo for carrier billing and MINT for prepaid. Brick Direct relies on client-side tokenisation: card details are exchanged for a one-time token, and the merchant's server then submits a charge or subscription request. The documentation also covers a 3-D Secure step and capture, void and refund calls. Brick Direct has to be enabled for a project by contacting the integration team, and the project must use HTTPS and have a pingback URL. See network tokenisation explained and the 3-D Secure guide for background.
Widget and Checkout requests carry a project key and a signature, with signature version 2 using MD5 and version 3 using SHA-256. The company describes a risk layer called Passport that draws on a cross-industry data network to verify customers and cut false positives.
Products
Brick: card processing
Brick accepts Visa, Mastercard, American Express, UnionPay and Maestro (products page). It is available as a hosted flow or through the Direct API, with subscriptions and the capture, void and refund operations noted above.
PayAlto: local payment methods
PayAlto covers bank transfers, prepaid cards, e-wallets and cash terminals. The company states more than 150 methods in about 200 countries on its products page, and more than 160 methods on an older support page last updated on 19 October 2020. Examples on the methods page include WeChat Pay, Alipay and UnionPay (Greater China), Boleto (Brazil), OXXO (Mexico) and Mercado Pago (Latin America). PayAlto can be integrated through the server-to-server Brick API for a custom form, or through a customisable hosted checkout page, plus reporting by API in CSV, XLS or PDF. See alternative payment methods explained.
SpiderPipe gateway
SpiderPipe links a merchant's existing acquiring accounts through one API and tracks them, which makes it a routing and reporting layer rather than a new acquirer. For the wider concept, see payment orchestration explained.
Invoicing, subscriptions and digital goods
eInvoicing creates online invoices payable by local methods. The Subscriptions product handles recurring schedules, custom packages and revenue recovery plans. The API reference also lists a Widget API for digital goods, with Tokidoki as a subscription management product.
Mobiamo and MINT
Mobiamo is mobile carrier billing and is priced for 80 or more countries. MINT is a prepaid card product with an ePIN API for generation and redemption.
Developer experience and integrations
The documentation site groups integration into four routes. Checkout API is the recommended hosted route and covers cards, alternative methods, carrier billing and prepaid for one-time payments and subscriptions. Direct API serves custom forms. Invoicing sends a Pay Button by email. The Widget API embeds a price-point selector and a product inventory for digital goods.
Server SDKs are listed for PHP, Node.js, Python, Ruby, Java and .NET, with mobile SDKs for Android and iOS, a Smart TV SDK and a Unity SDK. No-code plugins cover Shopify, Magento, WooCommerce, Wix and PrestaShop, plus hosting and gaming platforms such as WHMCS and Buycraft. A sandbox section provides a test payment method and a test pingback tool, and the Brick Direct API has its own sandbox page. PayAlto's Direct API was marked as coming soon on the overview page. Because pages are undated, check the documentation for current status before planning a build.
Payment methods, currencies and coverage
The methods page lists regional counts from the Caribbean to West Africa; the market index near its top shows 75 countries. Company-wide scale figures vary by page and none is dated:
| Figure | Page |
|---|---|
| About 150 local payment options, serving over 200,000 merchants | About page |
| Over 100 local methods through one integration; more than 300,000 merchants; 20+ global offices | Regional platforms release (June 2025) |
| 14 offices (5 Europe, 7 Asia, 1 North America, 1 Africa) | Products page |
The gap between 200,000 and 300,000 merchants is not explained, so quote neither as a current count. Support is described as available in over 30 languages on the About page. For emerging-market context see Rapyd and dLocal.
Pricing model
Paymentwall publishes a pricing page without a date. As opened on 3 November 2026 it states:
| Product | Published rate |
|---|---|
| Brick cards, EU-registered merchants, European cards | 2.1% + €0.25 per transaction |
| Brick cards, non-European cards | 3.9% + $0.30 per transaction |
| Possible cross-border surcharge | 1% on international transactions |
| Chargeback fee | $25 per chargeback |
| Rolling hold | 5% of revenue, returned if no chargebacks occur |
| Mobiamo carrier billing | 5% plus carrier fee |
| PayAlto local methods | 2% plus a method fee (bank transfers 1% to 5%, eWallets 2% to 7%, kiosks and cash 5% to 15%, prepaid cards 7% to 20%) |
| SpiderPipe gateway | Basic $0.10 per transaction; Advanced 2% per transaction |
| Account fee | $100 per month per business account |
Fees may vary with a merchant's risk level, and merchants processing more than $100,000 a month can request special rates. The terms of service describe a rolling reserve starting at 5% of gross transactions, released monthly from six months after processing, with the possibility of extra collateral. Monthly payouts are made within five business days of the first of the month, and amounts below $100 are held until they reach $100. Reserve terms matter for merchants in categories that acquirers treat as higher risk; see high-risk merchant accounts explained.
Recent launches
On 3 June 2025 (blog post dated 26 May 2025), Paymentwall announced five regional platforms: Brazipago for Brazil with Pix and QR support, NihonPay for Japan with PayPay, JCB and Konbini, SampanPay for Southeast Asia, KoreaPay for South Korea with KakaoPay, Samsung Pay and Toss, and TurkiyeCard for Turkey. The company says merchants do not need a local entity or bank relationship for KoreaPay. We did not find later dated launches on the pages we opened.
Regulation in brief
The terms of service say the contract is with Paymentwall Inc. and name Paymentwall Ltd (London) and Fasterpay Inc. among related entities, without saying which one applies to a given merchant. They do not name a payment licence or regulator; each party warrants that it holds the licences it needs, and card processing must follow PCI DSS and scheme rules. Merchants should ask which entity will contract with them and which licences it states; our guide to checking a financial licence explains how to verify them.
Who it tends to suit
Paymentwall may suit digital-goods, gaming, SaaS and subscription sellers that want card plus local-method coverage, carrier billing or prepaid options with a published starting price list. Merchants should weigh the monthly account fee and reserve against their volumes, and those with large volumes can negotiate. Teams comparing emerging-market specialists can also look at Rapyd, dLocal and Nuvei, and the gateways hub lists more.
Sources
Primary sources we checked for this page. Trademarks belong to their owners. Links open the original.
- Paymentwall: Paymentwall: accept payments worldwide (accessed 3 November 2026)
- Paymentwall: About Paymentwall (accessed 3 November 2026)
- Paymentwall: Payment products and services (accessed 3 November 2026)
- Paymentwall: PayAlto: worldwide local payment methods (accessed 3 November 2026)
- Paymentwall: Local payment methods (accessed 3 November 2026)
- Paymentwall: Pricing (accessed 3 November 2026)
- Paymentwall: Terms of service (accessed 3 November 2026)
- Paymentwall documentation: Integration overview (accessed 3 November 2026)
- Paymentwall documentation: Brick Direct (accessed 3 November 2026)
- Paymentwall documentation: API reference (accessed 3 November 2026)
- Paymentwall: Paymentwall launches global suite of specialized payment platforms (accessed 3 November 2026)
Get the weekly brief
New profiles, comparisons and payments technology explainers, once a week.
Information only, not financial or investment advice. CFDs are complex instruments and carry a high risk of losing money rapidly due to leverage. Crypto-assets are high risk and largely unregulated in some markets.
Payments30 is an independent publication of Humainz, Inc. We are not affiliated with, endorsed by or sponsored by the companies named on this page unless a page is clearly labelled as sponsored. Editorial policy.
Spotted an error? Report a correction. Companies can request a right of reply under our corrections policy.
