Payment Methods

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude

Payment methods are defined according to two different categories:

• Pull / Push: The merchant requests the funds from the customer, or the customer sends the funds directly to the merchant.
• Synchronous / Asynchronous: The charge happens immediately, or only after a period of time.

Pull or Push

Each method of payment is categorized as either pull or push, depending on how funds are transferred from the customer's payment method.

• In a method with a pull behaviour, the customer needs only to accept the payment request from the merchant. Credit card payments and MB WAY are examples of the described behaviour. On the credit card, the customer accepts the payment by providing his credit card details, while on MB WAY they accept by interacting with the push notification on the smartphone.

• In a method with a push behaviour, the customer takes the initiative of sending the funds to the merchant. Virtual IBAN or Multibanco are examples of such behaviour. On the Virtual IBAN, the customer should go to their bank account and create a SEPA transfer to the provided IBAN. On Multibanco, the customer should go to an ATM and create a payment to the entity and reference provided.

Available Payment Methods

Credit / Debit Card

A Credit / Debit card is a payment card issued to users (cardholders) to enable the cardholder to pay a merchant for a good or service. This is a synchronous pull payment method. This means that the payment happens immediately. Credit / Debit cards also support authorizations where you can hold an amount for later capture.

Characteristics:

• Type: Synchronous Pull
• Instant confirmation
• Supports authorizations and captures
• Supports 3D Secure authentication
• Works with: Single, Frequent, and Subscription payments

Test Environment Card Numbers:

• 0000000000000000 - Authorized for all operations
• 2222222222222222 - Proceed with 3DS authentication
• 1111111111111111 - Failed for all operations
• 1234123412341234 - Declined for all operations

Apple Pay

Apple Pay is a mobile payment and digital wallet service by Apple Inc. that allows users to make payments in iOS apps, and on the web using Safari. It is supported on the iPhone, Apple Watch, iPad, and Mac. Apple Pay is a synchronous pull payment method. This means that the payment happens immediately when the customer authorizes it using their Apple device. The merchant requests the payment, and the customer approves it on their device, which sends the payment to the merchant.

Characteristics:

• Type: Synchronous Pull
• Instant confirmation
• Requires Apple device
• Uses tokenization for security
• Works with: Single payments

Security: Apple Pay does not require the customer to create any additional accounts or fill out an extensive form for each purchase. It utilizes the cards already on file in a user's Apple Wallet. Apple Pay uses a method called tokenization to secure card information. Tokenization replaces the card number with a unique alphanumeric identifier, referred to as a token. The token is used for communication between the merchant, the bank, and Apple Pay, ensuring the actual card number is never shared with the merchant or transmitted with the payment.

Note: Apple Pay is not available in all regions and is subject to the terms and conditions of the card issuer.

Google Pay

Google Pay is a mobile payment method that enables customers to pay using credit or debit cards stored in their Google Account. It is a synchronous pull payment method, meaning payments are processed immediately upon customer authorization. Google Pay primarily uses a tokenized solution for enhanced security, which most issuers accept as compliant with Strong Customer Authentication (SCA), eliminating the need for 3D-Secure (3DS) in many cases.

Characteristics:

• Type: Synchronous Pull
• Instant confirmation
• Tokenized for enhanced security
• SCA compliant
• Works with: Single, Frequent, and Subscription payments

Fallback for Non-Tokenized Transactions: If a transaction isn't tokenized or the issuer requires additional authentication, the system will automatically trigger the 3DS flow to ensure payment success.

Compatibility and Requirements: Google Pay is fully compatible with existing features like recurring payments and can be integrated seamlessly into websites and apps. It requires serving the payment page over HTTPS with a TLS domain-validated certificate for secure transactions.

Usage: This payment method supports transactions for physical goods, donations, subscriptions, and more. The integration process involves enabling Google Pay in your payment methods settings, with minimal code implementation required when using certain payment platforms.

Important: All merchants must adhere to the Google Pay APIs Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

Samsung Pay

Samsung Pay is a mobile payment service allowing you to make contactless payments with your compatible Samsung phone or Galaxy Watch at most terminals that accept tap-to-pay cards. It uses NFC technology and your device's built-in security features for payments, not storing your actual card details with merchants.

Characteristics:

• Type: Synchronous Pull
• Instant confirmation
• Requires Samsung device
• Uses digital tokens for security
• Works with: Single payments

Key Benefits:

• Convenience: Make payments with your phone or watch, eliminating the need to carry cash or physical cards.
• Security: Uses a digital token for each transaction, so your actual card details are not stored on your device or shared with merchants.
• Fast and Easy: Payments are quick, requiring just a tap of your device.
• Wide Acceptance: Works at most retailers that accept contactless (tap-to-pay) card payments.

MB WAY

MB WAY is a Portuguese local method. To use MB WAY, the customer must have a Portuguese Banking account as well as a smartphone Bank/MB WAY app installed. This is a synchronous pull payment method. The Merchant will issue a payment request that will trigger a push notification on the customer application. MB WAY also supports authorizations where you can hold an amount for later capture.

Characteristics:

• Type: Synchronous Pull
• Instant confirmation
• Requires Portuguese bank account
• Requires MB WAY mobile app
• Supports authorizations and captures
• Works with: Single and Frequent payments

Test Environment Phone Numbers:

• 911234567 - Authorized for all operations
• 917654321 - Failed for all operations
• 913456789 - Declined for all operations
• 919876543 - Pending for all operations

Multibanco

Multibanco is a Portuguese local method. This is an asynchronous push payment method. The Merchant creates a payment request that will generate the Multibanco order details. The details include:

• An entity number
• A reference number
• The amount to pay

To pay, the customer introduces these details in an ATM or in their homebanking system.

Characteristics:

• Type: Asynchronous Push
• Customer-initiated payment
• Uses entity and reference
• Works with: Single and Frequent payments

Important Edge Cases:

• The customer can pay a different amount than the requested
• Multibanco refunds are not currently supported by the vendor. If refunds are needed, you can offer them via SEPA Transfer.

Direct Debit

Direct Debit is an asynchronous pull payment method in which a merchant withdraws funds from the customer's bank account. To do so, the customer must accept a SEPA Direct Debit (SDD) Mandate, which can be valid for multiple payments (therefore supporting single, frequent and subscription payments). To create the SDD Mandate, the merchant must supply the customer's name and IBAN.

Characteristics:

• Type: Asynchronous Pull
• Requires SEPA Direct Debit Mandate
• Confirmation may take up to 14 days
• Works with: Single, Frequent, and Subscription payments

Important Notes:

• Depending on the customer's bank, confirmations of Direct Debit payments may take up to 14 days.
• Direct Debit is not recommended for single payments due to the risk of fraudulent customers issuing chargebacks.

Test Environment:

• All valid IBANs will return success except: PT50000201231234567890154

Virtual IBAN

Virtual IBAN is an asynchronous push payment method that follows the same principles of SEPA Bank Transfers: the merchant provides the customer with an IBAN and transfer amount that they should introduce in an ATM or homebanking system to specify the bank account to which funds are to be transferred.

Characteristics:

• Type: Asynchronous Push
• Provides virtual IBAN for each payment
• Protects your bank account details
• Works with: Single, Frequent and payments

Benefits: In comparison with regular SEPA Transfers, Virtual IBAN has the benefit of protecting your bank account details by providing you with a virtual bank account number that supports single and frequent payments.

Important Note: Although transfers to a single-use Virtual IBAN after the first payment are initially accepted by the customer's bank (and thus funds are temporarily withdrawn), they are automatically refunded by the IBAN issuer bank.

Payment Method Comparison

Next Steps

• Payment Types - Learn about Single, Frequent, and Subscription payments
• Authorizations & Captures - Understand the auth/capture flow
• Quick Start - Make your first payment