Does the credit card surcharge apply to Afterpay, Google Pay and Apple Pay?

DJ P. shared this question 5 days ago
Answered

We have Square as our active merchant with Apple Pay, Google Pay and Afterpay all enabled, and Payment Preferences set to a 3.000% credit card surcharge (Apply Tax on Surcharge Fees = No).


On the Finalize Contract page, the "Buy with Google Pay" and "Buy with Afterpay" buttons render inside the Credit payment method, and the surcharge notice displays directly above them. On a test quote with a $140.43 required deposit it read "A payment surcharge fee of $4.21 will be added when using this payment method" — exactly 3.000%.


Two questions:


1. When a customer completes payment by clicking "Buy with Afterpay", is the 3.000% surcharge added to the amount actually charged, or does the surcharge only apply to a card typed into the card fields? Same question for Google Pay and Apple Pay.


2. If the surcharge IS applied to Afterpay, is there any way to exclude Afterpay from it while keeping it on regular credit cards?


The reason question 2 matters: Afterpay's own Merchant Terms of Service (Schedule A, section 2(c)) prohibit surcharging. The clause reads "Merchant must not impose a surcharge on the Customer for using the Payment Method. A surcharge includes any charge or increase in the sale price, shipping costs or any other Customer fees and charges that are applied because the Customer has elected to use the Payment Method."


If IO applies our card surcharge to Afterpay and there is no way to switch it off for that method, we would be in breach of the Afterpay merchant agreement on our very first Afterpay sale, and we would have to disable Afterpay entirely rather than risk it.


We have not taken an Afterpay payment yet and we are about to start promoting it, so we would much rather confirm this now than find out from a customer's statement afterward. Please let us know either way.


Thanks,

DJ Preble

Event Edge Rentals, LLC

Comments (3)

photo
1

The surcharge would be added if any of these are chosen the software does not know the difference.

Here is what google says about Afterpay:

In the U.S., credit card surcharges (extra fees added to a purchase for using a credit card) are generally allowed under federal law, with a maximum of 4% on credit card transactions Merchant Cost Consulting. However, debit card surcharges are illegal in all 50 states.

Afterpay is a Buy Now, Pay Later (BNPL) service that splits a purchase into four equal, interest‑free installments. When you pay with Afterpay, the merchant bills your linked credit or debit card for each installment. The Afterpay service itself does not charge you extra for using it — the cost is built into the installment payments cardix.us.

That said, some merchants have been reported to add an extra fee if you choose Afterpay. For example, one customer reported being charged $96 instead of $90 for a $90 item because “Afterpay is extra” Reddit. This is not a standard Afterpay fee; it’s a merchant‑imposed surcharge. Whether this is legal depends on your state’s laws:

  • In most states, merchants can surcharge credit card transactions up to 4% of the transaction amount Merchant Cost Consulting.
  • Some states (e.g., California) ban surcharges as separate line items but allow “dual pricing” or “all‑in pricing” (where the total is shown upfront) Merchant Cost Consulting.
  • In other states, surcharges are prohibited entirely (e.g., Texas, Georgia, Kansas) Merchant Cost Consulting.

Key points:

  • Afterpay does not add its own surcharge — the BNPL cost is part of the installment plan.
  • If a merchant adds an extra fee for using Afterpay, it’s a merchant surcharge, not an Afterpay fee.
  • Whether that extra fee is legal depends on your state’s surcharge laws.
  • In states where surcharges are allowed, the extra must be within the legal limit (often ≤4% of the transaction) and disclosed clearly.

Bottom line: You should not be charged more than the legal surcharge limit for using a credit card, and Afterpay itself does not impose such a fee. If you see an extra charge for choosing Afterpay, check your state’s surcharge rules and ask the merchant for clarification.

photo
1

Thanks Jen — that first line answers it, and it raises a bigger question I need to close out.


If the software cannot tell the difference between methods, then: does the 3.000% credit card surcharge also get applied to a DEBIT card typed into the normal card fields? Payment Preferences only has one "Credit Card Surcharge" field, with separate fields for PayPal and ACH but nothing for debit. So does IO do a BIN lookup and skip the surcharge on debit, or does it surcharge every card that runs through the credit path?


This matters more than the Afterpay question. Debit surcharges are prohibited by the Visa, Mastercard, Amex and Discover network rules in all 50 states, and our signed rental agreement tells the customer in writing that "Debit cards, cash, and checks carry no processing fee." If IO surcharges debit, we are breaking network rules and contradicting our own contract on every debit transaction, and I need to turn the surcharge off today.


One correction for the record, in case that reply gets reused for another customer: Georgia does NOT prohibit credit card surcharges. The Georgia Attorney General's Consumer Protection Division publishes guidance permitting them, capped at what the merchant actually pays to accept the card, with disclosure at the point of entry, at the point of sale, and on the receipt. https://consumered.georgia.gov/ask-ed/2021-03-03/credit-card-surcharges


Where I think this leaves us:

- Afterpay: surcharge applies and cannot be excluded. Afterpay's own merchant terms prohibit surcharging, so we will most likely disable Afterpay.

- Google Pay / Apple Pay: surcharge applies. Both can be funded by a debit card, which would make it a debit surcharge.

- Debit typed into the card fields: the open question above.


Please confirm the debit behavior and I will configure accordingly.


Thanks,

DJ Preble

Event Edge Rentals, LLC

photo
1

There isn't a spot on there that asks if the customer wants this ran as a debit, so it will always be a credit and yes the surcharge will be applied. So anything submitted under the CC option would have the surcharged applied.

photo
1

What I'm reading here is that IO opens the door for legal issues if someone uses a debit card, even ran as a credit card, because we're still charging a fee for that? From what I've read, the law does not distinguish whether the card is run as debit or credit, but rather what the card is tied to, A line of credit or a bank account.

photo
1

Using a debit card requires entering a pin number and the software does not ask for a pin number, so therefore the card information that is entered would be ran as credit rather than debit from my understanding.

photo
1

Right, but from what I understand of that the law still treats that as a debit card ran because it's tied to a bank account. Regardless of how it's ran, it's what account is tied to it

photo
1

I'm going to have a developer look further into this and the ticket will be updated.

photo
1

Per our Developer:

Thank you for raising this and for giving us the opportunity to investigate it fully. We reviewed the checkout code, your current account configuration, your IO transaction history, and the corresponding Square payment.

Afterpay

Yes. When a nonzero Credit Card Surcharge is configured, IO adds that surcharge to the amount sent to Square when the customer chooses Afterpay. The surcharge notice is not merely associated with the card fields—the total passed to Afterpay includes it.

IO currently has no setting that excludes Afterpay while retaining the surcharge on ordinary credit cards. Because this is an online checkout, applying the surcharge would conflict with Afterpay’s merchant terms, which prohibit increasing the customer’s price because Afterpay was selected. (Afterpay Merchant Terms)

With your surcharge currently set to 0%, Afterpay can remain enabled without IO adding a surcharge. If you re-enable a nonzero surcharge, the present alternatives are to disable Afterpay or accept that IO will include the surcharge; there is no selective exemption today.

Google Pay and Apple Pay

The same behavior applies to Google Pay and Apple Pay. IO calculates one surcharged total before the Square payment method is processed and sends that total for card, Google Pay, Apple Pay, or Afterpay.

IO does not inspect the wallet’s underlying funding type before adding the fee. Consequently, a wallet funded by a debit or prepaid card can also receive the surcharge. There is currently no separate exclusion for either wallet.

Debit cards entered in the normal card fields

IO does not perform a BIN lookup or otherwise distinguish credit, debit, and prepaid cards before calculating the surcharge. It treats every payment submitted through the Credit payment option as surcharge-eligible.

Entering a debit card without a PIN does not convert it into a credit card for surcharge purposes. It remains a debit card even when processed as a keyed or signature-based transaction. Visa expressly states that debit and prepaid cards cannot be surcharged, including when “credit” is selected at the point of sale. (Visa surcharge guidance)

We confirmed this behavior against one of your actual payments:

  • Lead #69987807
  • July 4, 2026
  • Base payment: $53.50
  • Surcharge: $1.87
  • Total: $55.37
  • Square classification: Visa debit, not prepaid
  • Entry method: keyed
  • Not Apple Pay, Google Pay, or Afterpay

The $1.87 was an untaxed 3.5% surcharge. In addition to being applied to a debit card, 3.5% exceeds Visa’s current credit-card limit of the merchant discount rate or 3%, whichever is lower.

Before issuing any correction, we should confirm whether this payment has already received a partial refund. If it has not, the $1.87 surcharge should be refunded through the normal IO/Square refund workflow.

Your current configuration

Your current production settings show:

  • Credit Card Surcharge: 0%
  • Apply Tax on Surcharge: No
  • Apple Pay: enabled
  • Google Pay: enabled
  • Afterpay: enabled
  • Square: connected

Therefore, newly loaded checkout pages should not add a surcharge to any Square payment method now.

We found no Square transaction around the date of your report and no completed Afterpay transaction. Your August example was a proactive checkout test rather than a completed charge. The only historical customer Square payment we found was the July debit transaction described above.

The evidence shows that the account had an effective 3.5% surcharge in July, displayed 3% in the August test, and is now set to 0%. Payment Preference changes are not audit-logged, so we cannot provide the precise time each setting changed.

Georgia correction

You were also correct to challenge the earlier statement about Georgia. Georgia permits credit-card surcharges subject to restrictions, including that the surcharge not exceed the merchant’s acceptance cost and that it be properly disclosed. (Georgia Attorney General consumer guidance)

State rules and card-network rules are separate considerations. Even where a state permits credit-card surcharges, Visa’s debit/prepaid prohibition and applicable credit-card limits still apply.

We have documented the broader software limitation for product review. Until IO can distinguish the payment method and funding type before calculating the fee, keeping the Credit Card Surcharge at 0% is the safe configuration if Afterpay, wallets, and debit-card acceptance remain enabled.

photo
Leave a Comment
 
Attach a file