Bank Payments at Checkout
Customers link their bank account and approve the payment, with no card number to type and no card to expire.
Pay by Bank
Pay by Bank: Accept Payments Straight From Customers' Bank Accounts
Pay by bank lets customers pay directly from their US bank account instead of using a card. Soap adds pay by bank to your checkout next to cards and wallets, and lets you send payouts back to bank accounts, through the same integration.
01
US bank payments next to cards and wallets in one checkout
02
Payouts to customers' bank accounts, instant where their bank supports it
03
One integration and one dashboard for every payment method
Core Capabilities
Infrastructure for the operational realities of pay by bank
Bank Payouts
Send withdrawals and other payouts to bank accounts, in real time where the receiving bank supports it and by same-day ACH where it doesn't.
Next to Cards and Wallets
Offer pay by bank alongside cards, Apple Pay, and Google Pay, so customers pick the method that works for them.
One Integration
Bank payments, cards, and payouts run through one hosted checkout and one dashboard, so your team doesn't run separate systems.
15+
Processor Relationships
93%
Approval Rates
<0.3%
Chargeback Rate
Where It Fits
Typical teams and payment flows
Soap is a fit for teams managing high-frequency payments, more complex settlement paths, or tighter operational and compliance requirements than standard checkout stacks can handle.
Businesses with larger order values, where card fees add up
Platforms that collect from customers and pay out to their bank accounts
Merchants whose customers prefer not to use a card
Businesses adding a lower-cost payment option next to cards
In Depth
How Soap works for pay by bank
What is pay by bank?
Pay by bank is a way to pay online directly from a bank account. Instead of entering a card number, the customer connects their bank account and approves the payment, and the money moves from their account to the merchant over bank payment networks. These are sometimes called account-to-account payments. For customers it can feel as simple as a card checkout. For merchants it adds a payment method that doesn't depend on card networks.
Why merchants add pay by bank
Bank payments usually cost less to accept than card payments, which matters most for larger orders. There are no card numbers to store or cards that expire, and customers who prefer not to use a card get another way to pay. Pay by bank works best next to cards, not instead of them: customers choose the method they trust, and you keep the payments that a card checkout alone might lose.
Pay by bank with Soap
Soap adds pay by bank for US customers to the same hosted checkout you use for cards and wallets, so there is no separate integration to build. Payments and payouts show up in one dashboard, next to every other payment method. Soap can also send payouts to bank accounts, so the same integration covers money in and money out.
FAQ
Common questions from pay by bank teams
How does pay by bank work?
The customer chooses pay by bank at checkout, connects their bank account, and approves the payment. The money moves from their bank account to the merchant over bank payment networks, without a card.
Is pay by bank cheaper than cards?
Bank payments usually cost less to accept than card payments, especially for larger amounts. Talk to the Soap team about pricing for your business.
Can I offer pay by bank and cards at the same time?
Yes. Soap shows pay by bank next to cards, Apple Pay, and Google Pay in one checkout, through one integration.
Can Soap send payouts to bank accounts?
Yes. Soap sends payouts such as withdrawals to US bank accounts, in real time where the receiving bank supports it and by same-day ACH where it doesn't.
Which countries does pay by bank cover?
Pay by bank and bank payouts with Soap are for US bank accounts today.
Related Pages
Explore adjacent categories
Next Step
Build the payments layer around how the business actually operates
Soap brings routing, onboarding, fraud controls, and compliance operations into one stack so teams can scale without duct-taping more infrastructure together.