How do you process payments?

For my consulting business (average invoice size of anywhere from $15k-$125k), we exclusively accept paper checks, ACH (either as a direct credit for larger companies set up to do that,) or QuickBooks Online, which makes ACH relatively trivial, and they charge basically $1 to process it. Can't beat that with a stick.

For our clients, our preference is still Stripe, though we had a client deplatformed by them because their bank had problems with the product. (In our case, specifically, adult toys.) We had spoken with Stripe at length before investing in using them, and confirmed that this would be acceptable, as they had other adult toy companies on their platform, but Wells Fargo, paragons of fucking virtue that they are, decided to step in an try to get extremely and very awkwardly hands on with our specific products. (They tried to dictate what colors we could and couldn't offer, for instance. It was unpleasant, and we recognized we needed to leave immediately.)

We ended up back at a higher-risk merchant service provider, though we're paying typical rates because we fulfill an actual, physical product (not, say, porn), and our chargeback rate is very low. Still a frustrating experience, and yet another reason to hate Wells.

Stripe whenever it's possible. However, without PayPal one is missing a bug chunk of people who cannot pay with credit card. Hence, I offer both. Since I implemented both (again) over the last month, here a list of my resources:

- Stripe Elements [0] + Stripe Webhook [1]

- Stripe Checkout [2] + Stripe Webhook [1]

- PayPal Smart Payment Buttons [3]

And one repository:

- basic Stripe Checkout with Webhook in React + Express [4]

Personally I preferred Stripe Checkout over Elements, because they take care about the look and feel.

- 0 https://github.com/stripe/react-stripe-elements

- 1 https://stripe.com/docs/webhooks

- 2 https://stripe.com/docs/payments/checkout

- 3 https://developer.paypal.com/docs/checkout/

- 4 https://github.com/rwieruch/react-express-stripe

We use Chargebee backed by Stripe.

We've been quite happy with Chargebee overall and would recommend them. The only downside is their customer support is very bizarre sometimes and a bit frustrating.

For example, they limit API access to my own (events) data to the last N months. I contacted and asked them to remove the restriction, and they said that wasn't possible because the data was "archived". I pointed out that their UI allowed me to see all the data and their page loaded quickly so clearly the data is close at hand. They then said they'd give me access to all my data over the API for one week. I told them I'm not going to build a script that will be broken in a week and instead will just have to scrape their website - they seemed happy with that resolution.

I operate a "electronically supplied services" hobby company, https://webhook.site, and I just didn't want to deal with VAT payments to individual EU member countries. So I switched from Stripe to Paddle, who handle all the VAT payments for me, take a fee and give me a lump sum. EU just has way too much bureaucracy for small-medium sized companies. I'm also using Patreon which is similar (they also handle VAT and subscriptions), but it seems most people prefer Paddle to Patreon.

Tangentially, I'd recommend everyone to stay away from Paypal. You will lose your money or your account sooner or later. Let someone else (like Paddle) handle Paypal payments and that risk.

Stripe when possible, but for a recent project I’m using Dwolla, which operates strictly via ACH (which makes it US-only).

The problem with Stripe is they have a large list of prohibited businesses, which mainly is inherited from the credit card networks as I understand it. Even if you’re a perfectly legal and legitimate business, if you fall under one of these broad categories you can’t use Stripe’s platform (even if you only use their ACH product and don’t touch credit cards). PayPal has a similar list.

The credit card networks justify it by claiming certain categories of business are riskier (and I’m sure some are). But then you see how a lot of these categories may have come from Operation Chokepoint, chosen by unelected bureaucrats seemingly without any evidence.

Personally it disturbs me that so many legitimate businesses are severely hamstrung from collecting payments online because of extremely opaque decisions by an oligopoly of payment networks.

But about Dwolla - it’s not quite as smooth as Stripe; you have to build out your own customer onboarding screens, and production plans are priced through a sales rep rather than a SaaS-y paygo model. But I feel much more in control from the business end of things using them.

I've been selling a SaaS product for the last four years. Originally I used Stripe but recently switched to Paddle.

The main reason is that it makes my life a lot easier, they act as a reseller so I effectively sell my product to them, and they sell it on to customers. At the end of each month I just need to enter a single payment into my accounting platform, and they handle all currency conversions (I sell in USD, my accounting is in GBP) and sales taxes. They of course charge more, but for the amounts I'm talking about the cost outweighs the time I was spending dealing with Stripe payments.

They also support PayPal which I've had a lot of people ask for, so that's a win too.

We use Stripe to process credit card payments and we're adding support for ACH soon. Recently they made some changes to pricing (charging for Radar and non-US cards) that was surprising but otherwise they've been amazing. Great tooling support, great customer service and overall great platform.

We[1] use Stripe[2], Braintree[3], Coinbase Commerce[4], and GitHub Marketplace[5].

We built our own quote logic including prorating, etc. then apply that as recurring subscription using Braintree if customer wants to pay with PayPal, or Stripe if customer wants to pay with credit/debit card.

Breakdown by processor:

73% Stripe

26% Braintree/PayPal

0.7% GitHub Marketplace

0.3% Coinbase Commerce

[1]: https://wakatime.com/

[2]: https://stripe.com/

[3]: https://www.braintreepayments.com/

[4]: https://commerce.coinbase.com/

[5]: https://github.com/marketplace

I have a small side business that makes a physical product. I've used PayPal for years with no issues, touch wood. There are two things that I like:

1. I don't have to write code or maintain a server to process payments. I realize that I'm an outlier for not wanting an API, but my business web page is completely static, and it's convenient for me to keep it that way.

2. They are unified with USPS for shipping, which has the best rates and service for packages that weigh just a few ounces. I can click on a button in PayPal and it spits out a USPS shipping label for me.

I greatly prefer not having to handle any of my customers data. The only info I ever see is their shipping address and whatever e-mail address they signed up to PayPal with.

Our company is based out of India selling online courses for Data Science community and we use two payment providers: Instamojo and Paypal. Instamojo is for Indian cards and Paypal is for international payments. We could have used Instamojo for all payments but many customers like using Paypal as they don't have to worry about saving credit card information with some random payment provider.

Stripe just came out of private beta in India but their processing fees are pretty high. We are looking at two providers as they are promising better fees. Razorpay and Payu:

- Razorpay is pretty much Stripe of India with the documentation and UI similar to Stripe.

- Payu is an old dog in Indian Payment Industry with good sales team but bad integration and overall product.

I use Paddle, because they handle the intricacies of international VAT which is getting more and more complicated. I'd love to use Stripe, but I'd have to use something like Taxamo in combination with it. Since I was one of their first B2B customers I managed to negotiate a good rate with them, otherwise they'd be reasonably expensive. I've been generally happy with them.

I use Stripe and PayPal. PayPal accounts for about 30% of my revenue. As another data point, I get easily 10x more requests for Stripe integration on https://divjoy.com than all other payment options combined. Devs overwhelming want to use Stripe.

Pin Payments, for cards.

They have an Australian focus but global capability. If you use a scheme card for Fastmail, you probably paid via Pin Payments.

Pin have a Stripe-like API but a small-team feel during contact i.e. we know one another by name, and when escalating a technical query I've had dialogue directly with a dev lead. I've even received hand-written Christmas cards from them.

I live in mortal terror of Pin being bought by Stripe, or (worse) an Australian financial institution, with all the consequences for competence and customer service level that follow.

We also handle bulk/large payments via CS2 (the Aus equivalent of ACH, for Usonian readers), with handling fee.

Authorize.Net is what we've used for online payments and our internal subscription processing for over a decade. API is easy to use. Never really had any downtime. Rates are competitive. No one has come along and given us much of a reason to change.

The FDA/DEA have waged war on the kratom industry in extralegal fashion; I've had my personal bank accounts and credit cards shut down without explanation via https://en.wikipedia.org/wiki/Operation_Choke_Point.

With Operation Chokepoint over, the DEA/FDA still have colluded to prevent the kratom industry from processing credit cards. For my website www.getkratom.com, we take checks, echecks, and cryptocurrency. Sales are about 1/3 of what they were when we were able to take credit cards.

I use https://pinpayments.com/ to accept credit/debit cards. My target market is 100% Australian so it was an easy option for me, but it won't be suitable for most people here.

100% PayPal, despite the horror stories. Why? Micropayment account alongside regular account. A majority of payments are less than US$12, many are US$1 and on the latter I save 23c per transaction over typical rates (PayPal or other processors).

Customers from Turkey, Pakistan and a few other places are not happy (PayPal banned in their territories), but for the most part, few complaints. Ancient key/value pair API continues to work, which is nice.

Hate their website, hate the lack of ways to get reports, particularly on subscriptions.

Could be done so much better (and likely is), but the micropayment account saves me thousands of dollars a year.

Stripe for credit cards, run own nodes for cryptocurrency because customer privacy is important in certain scenarios for me.

I am also interested in this question but would also love to know the average percentage people are paying. It’s always been interesting to me how stripe (and the like) are basically a premium over less polished tools like Authorize.net but are able to charge as much as a percentage point more for basically the same thing.

I’ve built payment integrations my entire 20 year career and have always appreciated how ease of use relates to cost, e.g. it’s hard to build tools as easy to use as stripe or Braintree, but I’ve wondered how these features play out when it’s so close to the actual money itself.

I'm actually implementing our Stripe integration as we speak. Super straightforward to get it done, with tons of documentation and example, and the Elixir library is fantastic.

Exclusively Paypal. I've had nothing but extremely positive experiences, but form what I hear, when it goes bad, it goes really really bad. I'm looking into other options

We use both Paypal and Stripe for international (worldwide) payments. Most customers seem to prefer Paypal, and Paypal is set up so that we don't have to do anything - we just receive an email on purchase, while we need a server in the middle for Stripe.

Paypal is significantly more expensive. Recurring subscriptions are really bad (the "vintage" UI is stuck circa 1999).

But what's really bad is that at some point, after 5 or 6 years of significant usage, someone calls us once at 4.30 PM, gets no answer, and flags us as "suspicious". At that point, we could not retrieve any money for the account, could not call anyone (you cannot contact the fraud team - we'll call you back), and it started a lengthy (like, a couple of months) process where we were asked a lot of previous information in order to unlock the account. I mean, I understand you may want/need more information, but you talk to us first and then, if you do not receive good answers, you lock the account. Our bank charges per year way less than PayPal and gives us an account who knows who we are, comes visit yearly, and whose mobile number I have.

So, even if we still use Paypal by popular demand, I'd rather not.

Stripe and an in-house Bitcoin backend

Funny thing is that I'm working on debugging an issue with the Stripe API right now (or the library I'm using)

Elavon for direct card (they supported 3DSecure early back in the day), PayPal, and Bitcoin. We used to support Western Union, but we got blocked after a random amount of funds was received, their support was not able to help.

Business is for digital goods.

Would like to support worldwide bank transfers if it can be safe and quick for both sender and receiver, anyone got any tips?

For Nordic/European customers, you should check out Mondido, which provide local payments and a lot for smart added value.

We use Stripe for usage-based billing of our video calls API.

We wrote a blog post about how we built on top of Stripe's "subscriptions" API: https://www.daily.co/blog/implementing-api-billing-with-stri...

Multiple businesses but most common is direct wire transfer/bank transfer. The smaller business: generate invoices, send them to the customer, customer has a few choices, the only international ones are IBAN or PayPal (adds fees). Most common used is direct bank transfer. AVG transaction: €2500. Larger business: mostly commerce payments, over 90% is iDEAL (Dutch native payment system - does instant wire transfers between Dutch banks), the rest is either Apple Pay or by invoice/manual bank transfer. Some sub-0.1% uses Credit Cards but it almost costs more to keep it available than the revenue it generates. In all cases we use native banking APIs, no middlemen/broker/processors, except Credit Card. AVG transaction: €50.

Has anyone used Payfort (now an Amazon subsidiary), which is a payment processor for GCC (and MENA?) countries? I've never used them, but their terms of service seem to explicitly prohibit being used for software sales. I was wondering what else is available in the GCC countries that permits software subscriptions. For example, Chargebee seems to support transactions in AED, but it is not clear whether they can be used, for example, by an UAE-based LLC.

Bitcoin.

At our price range (most invoices are $10k-$50k and in the US), we generate and send invoices from Xero, our accounting software. Customers can pay via check, wire, ACH or Credit Card, and they typically do checks or ACH. For additional context: we automate customer service for ecommerce companies in the 50-500 employee range. Payment methods vary depending on the company size, localization, sector, payment size, etc.

Stripe.

Love the developer friendly aspect, and their customer service is awesome.

Due to a misunderstanding[1], they believed our service violated their TOS. Stripe offered us a week to migrate AND suggested a competitor that allows those types of Txns.

Luckily, with a message to Customer Support (via Twitter) we resolved the misunderstanding and never had to migrate.

Also worth noting, the issue was addressed on a Saturday.

1: Stripe mistakenly thought we were doing online prescriptions.

We used GoCardless to set up Direct Debits. We were taking large-ish recurring payments (£100s) and GoCardless was the cheapest as they cap at £2 a transaction.

Their service was great and was trivial to interact with. We were working only in the UK, and Direct Debit isn't available everywhere but GoCardless offers some equivalent in a lot of countries.

We use MangoPay.

The customer service or tech support isn't as great as Stripe but they have a really intuitive model for marketplaces

I’m in the process of starting up a side business for my wife, making and selling physical goods. I’m in Sweden, and the go-to here is Klarna. They have their issues, but integration with WooCommerce was a breeze and people have come to expect Klarna as the default way to pay online.

I'm a complete dinosaur using Paypal. It emails me when there's a payment and I manually respond to the customer. They have to wait until I check my email since I don't even get notifications. Sorry customers. Paypal is a nightmare of course. Don't be like me.

At my current company we use Spreedly to integrate with the payment gateway. Idea is to have multiple payment providers in the background, which is fairly simple with Spreedly (they offer a single API, while large nr of supported psps in the background).

We also vaulting the cards there.

Stripe

Several of my hospitality clients have started with Square. The CC fees are straight forward <= %4.

There are third-party partners who extend on the platform. (I'm looking for a simple option for invoices-statements without trying to compete as Online Bookkeeping service.)

We used both stripe and paypal. Now we have consolidated everything to stripe. Larger payments we use paper checks and wire transfers. Pricing wise both paypal and stripe are not very different.if you process large amounts you can get discounts from both

Chargify. JUST DON'T DO IT! It's very limiting, the api sucks, and it's expensive. We got locked in by a dev before I was a part of things and I think before Stripe (maybe not.) Either way; just don't.

I create invoices using invoiceninja, which are payed via banktransfers mostly and via mollie payments for the smaller amounts.

This is usually an ideal payment in .nl, and various other payment methods in other european countries.

I own my own payment processing company and gateway, so I use that. I do sometime recommend Stripe and Square to Clients but Stripe for most people is a no go in Canada because of the 7 day deposit delay.

Services work invoiced through Bonsai, typically paid via ACH with some credit cards mixed in. Stripe handles the ultimate money movement.

SaaS - mostly Stripe credit cards, with a tiny percent in PayPal.

We use Stripe, Braintree (just for paypal billing agreements) and Mollie for certain EU payments. Mollie we only do annual payments since they are mostly non recurring payment options.

Paypal. Never had issues with them. Only problem is there are a few customers that are dishonest but they are just a couple of them Every year. Average transaction is 15usd

Every client pays via CC except one by check and one by ACH. We use WePay which is connected to Freshbooks. We eat the 3% charge or whatever it is. Avg order size of $2,000.

We use Paystand for Credit Cards (2.49% + 30¢), ACH and eCheck 25¢ 0%. Services business. Import transactions into Xero. Monthly fee $299. We pass the CC fee to customers.

We use Stripe. Will be adding PayPal integration later this year. Many of our customers are in europe and they don't have credit cards. PayPal works best for them.

Nobody have experience with 2checkout? I'm considering using it for a SaaS (they handle taxes, payout to latam), but the lack of references feels odd

A mix of Stripe and Shopify's own billing system.

Braintree, planning to switch to stripe. Still looking for a good EU-compliant (Poland) solution for invoicing, having to do it myself right now.

Stripe's Payment Intent API

All done via serverless functions, for both initialisation and confirmation(via Stripe's webhooks).

Ebanx, for the Latin America market.

Adyen is a large player. Not quite as slick as Stripe but better rates.

Oh, what about sales tax for SAAS in USA? Currently driving me mad.

Stripe/paypal

Elavon

Java:

public class PaymentRequest{}

public class PaymentResponse{}

Golang:

type PaymentRequest struct {}

type PaymentResponse struct {}

Kotlin:

data class PaymentRequest("")

data class PaymentResponse("")