Skip to content

    Payment methods

    This guide shows which payment methods are supported by Checkout, how they can be added and how that affects both, the payment flow and how to process these payments.


    Checkout supports a variety of payment methods to provide convenience for your consumers. This ranges from:

    • Account to account (A2A)
    • Cards
    • Wallet based payment methods
    • Invoices
    • Installments

    Please note, that certain payment methods such as Swish, Vipps, RatePay must be enabled in the configurations of your Checkout Account. Which of these appear on your payment window for your customers to choose from, might depend on your country and currency settings.

    Supported payment methods

    SEPA Direct DebitA2ADE, AT
    TrustlyA2AAT, CZ, DE, DK, EE, ES, FI, GB, LV, LT, NL, NO, PL, SE, SK
    American ExpressCardsAll
    Visa & MastercardCardsAll

    You can find more in-depth information, including countries, currencies, testing, functionality of payment operations, etc. in the relevant linked sections.

    Authorization times for charge, cancel and refund

    Payment methodGuaranteed captureCapture but not guaranteedCancelRefund
    --180 days after capture
    7 days
    30 days7 days180 days after capture
    7 days
    30 days7 days180 days after capture
    7 days
    30 days
    7 days180 days after capture
    American Express
    7 days
    30 days7 days180 days after capture
    Forbrugsforeningen7 days30 days7 days30 days after capture
    Apple Pay
    7 days
    30 days7 days180 days after capture
    AfterPay30 days30 days180 days after capture
    RatePay30 days30 days180 days after capture
    PayPal30 days30 days180 days after capture


    Charge, also known as capture in this context, outlines whether the amount is reserved or not:

    • Guaranteed capture means that the amount is reserved, and that you are guaranteed to collect the amount.
    • Not guaranteed capture means that the amount is NOT reserved any longer. But you can still try to capture the amount.

    You can read more about charges from here.


    Refunds can still be done up to 365 days after capture as Checkout keeps the data of the transaction for 1 year.

    You can read more about refunds from here.


    If you are canceling the payment then you are releasing the reservation which means that it will block you from doing the charge.

    You can read more about cancellations from here.


    A credit card authorization is a request to a card issuer from a card acquirer to approve a request for funds on a cardholder’s account. The request is based on a purchase transaction between a cardholder and you.

    In the process of the authorization request, the card issuer will check if the consumer has:

    • an active card
    • their card is not reported as stolen
    • the request does not seem fraudulent
    • the cardholder has sufficient funds to cover the cost of the transaction

    Once an authorization is approved, the amount is reserved and it can be captured. This means that transfer of funds occur upon capture.

    However, please note that funds are only reserved during a limited time period. After this time period has exceeded, the issuer is not required to honour (to approve) the capture request.

    The timeframe for authorization time for the different card schemes can be seen in the above table.


    Vipps, MobilePay and Apple Pay transactions are processed according to the underlying card scheme’s rules i.e. Visa, Mastercard, and Dankort etc.

    You can check the table above for the individual card scheme rules.

    Account to account (A2A)

    We currently support A2A payment methods such as, Swish, Trustly and Sofort. These funds are settled instantly to your account, with the key requirement that there is balance on the consumer's account.

    Strong customer authentication

    Checkout is Strong Customer Authentication (SCA) compatible which means that 3D Secure is mandatory for all payments.

    Whenever a consumer goes through the checkout flow with any given payment method to pay, the SCA will be triggered.

    Some exemptions occurs for the SCA trigger but these lies on the issuer's side. This means that the SCA is not always triggered for example for cards and wallets. A use case for this could be a low value exemption where an order amount is under a certain value where it is not needed to go through SCA for the consumer.

    You can see all of the individual payment method types user journey from here to see how and when the SCA is triggered:

    For cards, you can read more here.

    For more information about SCA, you can check this page here (in Danish).

    3D Secure

    The 3D Secure simulator as seen below makes it possible to either approve or decline a payment. The following image is taken from the test environment.

    3D Secure simulator

    Consumer information required

    In order for consumers to be able to use invoice and installments (AfterPay-Riverty and Ratepay-invoice) payments in the checkout process, we need to receive the consumer information and address.

    Was this helpful?

    What was your feeling about it?