Skip to main content
Payment methods need more buttons than other areas of the shop because the data must be checked before the order can continue. For bank data, this happens in two steps; for external payment services, the service itself takes over part of the flow. The tags on this page fall into three areas: bank data in the customer account and on the order overview, the search in saved payment data, and the buttons of the connected payment services.

How the BT tags work

A BT- tag outputs the technical name of the button, not its label. The shop uses this name to recognize which button was clicked.
The tag goes into the name attribute, the text for the buyer into value. The button must submit and must be inside the associated form.

Bank data

Entering the bank details takes two steps. In the first step, the buyer enters IBAN and BIC; in the second, they confirm the bank determined by the shop. Four tags map this flow.
BT-BankProof, BT-BankChange and BT-BankSubmit are also range tags. This is not a gimmick: the enclosing range shows each button only in the step where it makes sense. Without it, the “change input” button appears before there is anything to change.
BT-Bank_Refresh appears in older documentation as BT-Bank_refresh. Both spellings work because the shop resolves tag names case-insensitively.

BT-BankSelection_OK

Applies the selection of a saved bank account on the order overview page. This tag is also a range tag and thus indicates whether several bank accounts are available for selection at all.
Reference: BANK- (bank data)

Credit card selection

BT-CCardSelection_OK

Updates the selection of the saved credit card on the order overview page. As a range tag, the button only applies if the buyer is logged in and saved credit card data exists.
The button is the fallback for disabled JavaScript, just like BT-BankSelection_OK for the bank account. With JavaScript, the selection list triggers the update itself.
Reference: CC- (credit card data)

Searching saved payment data

Business customers often have several bank accounts and credit cards stored. Two tags trigger the full-text search in them.
Both buttons must be inside the form listed for them. In any other form on the same page, the search has no effect.
Guide: Offering full-text search for multiple customer data

PayPal Express Checkout

With Express Checkout, the buyer starts the order directly in the basket and then returns with the address and payment method from their PayPal account. Three tags are involved, and they are located on two different pages.
The cancel button is required. The buyer started the checkout via PayPal and cannot get back to another payment method without it.

BT-PPCVault_refresh

Outputs the name of a hidden button for PayPal Checkout with Vault. It is not clicked but triggered via JavaScript.
The button is intentionally empty and invisible. The payment service’s JavaScript triggers it as soon as it has applied a stored payment source.
Guide: PayPal Express Checkout · PayPal Checkout with Vault

Klarna Payments

BT-KlarnaPayments_cancel

Cancels the order with Klarna.
As with Express Checkout, there is no start button in the BT group here. Klarna is chosen via the normal payment method selection, and only cancellation needs its own tag.
Guide: Klarna Payments

Tag overview

None of them is a loop tag.
  • Guide: Creating payment methods
  • Guide: PayPal Checkout
  • Reference: BANK- (bank data)
  • Reference: Buttons in the order process