Bank Transfers

Transfers via Open Banking channels

The gateway is integrated with a broad network of European banks via their Account Servicing Payment Service Providers (ASPSPs). This allows real-time access to customer accounts for payment initiation.

List of available Regions and Banks

Baltic States

  • Swedbank (A2A, Transfers, Recurring)

  • SEB banka (A2A, Transfers, Recurring)

  • Citadele Banka (A2A, Transfers, Recurring)

  • Luminor Bank (A2A, Transfers)

  • Signet Bank (A2A, Transfers)

  • Industra Bank (A2A, Transfers)

  • Magnetiq Bank (A2A, Transfers)

Nordic

  • Danske Bank

  • Jyske Bank

  • Sydbank

  • Nykredit Bank

  • Spar Nord Bank

This service "Transfers via Open Banking channels" available for our solution in Delivery mode This service, "Transfers via Open Banking Channels," is available as part of our solution in SaaS delivery mode or as a standalone aggregation service.

Access to banks will be conducted on behalf of your license, with Tietoevry acting as a Technical Service Provider (TSP). As a TSP, Tietoevry does not provide regulated payment services or hold a payment institution license but facilitates secure technical connectivity between your system and financial institutions.

More about Tietoevry API Aggregation Service: https://aggregation.api.tieto.com/

Regulatory and Compliance Considerations

  • The licensed entity (you, the customer) retains full responsibility for ensuring compliance with applicable financial regulations, including but not limited to PSD2, local regulatory requirements, and AML/KYC obligations.

  • Tietoevry provides technical enablement and infrastructure support but does not assume liability for any regulatory breaches, transaction disputes, or legal obligations related to financial operations.

  • The scope of banking access and supported regions is determined based on regulatory approvals and licensing coverage of the customer.

For discussions regarding regional extensions, additional banking integrations, or compliance requirements, please contact us to assess feasibility and regulatory alignment.

Added Value service

Dynamic ASPSP Selection

The gateway continuously monitors the status of ASPSPs in real time. When a customer initiates a transaction, the system dynamically filters and displays only banks that are currently operational. This approach reduces the likelihood of failed transactions due to bank unavailability or downtime during the payment process.

Real-time status checks are conducted via direct API calls to ASPSPs, ensuring the customer is presented with only viable payment options.

Refund Support

Refunds for A2A transactions can be initiated via the Merchant Portal or through the refund API. The gateway communicates directly with the customer’s bank to reverse the transaction.

Both full and partial refunds are supported, with transaction statuses tracked and updated for transparency.

Supported solution simplifies post-payment workflows for merchants, ensuring compliance with refund policies and improving the customer experience.

Recurring A2A Payments

Customers grant consent for recurring payments during the initial transaction. The gateway securely stores authorization details for subsequent transactions in compliance with PSD2.

Recurring payments are triggered automatically on a predefined schedule, with confirmation messages sent to customers and merchants for each payment.

The proposed solution is suitable for subscription-based services or businesses requiring predictable payment cycles.

Deployment and Integration capabilities

he Tietoevry E-Commerce Payment Gateway supports modular and flexible integration with Open Banking APIs to enable A2A (Account-to-Account) payments via regulated Payment Initiation Services (PIS). The integration approach allows institutions to choose the most suitable strategy based on their market coverage, infrastructure, and regulatory preferences.

Open Banking-based A2A payments are enabled through the Payment Initiation interface of PSD2-compliant APIs and rely on the end-user’s bank for authentication and authorization.

Integration Models Supported

Integration Model
Description
Market Focus

Tietoevry acts as a regulated Third-Party Provider (TSP) and provides direct access to Open Banking APIs in selected markets. EGW leverages this service to offer a pre-integrated, compliant PIS channel.

Bank-Owned API Aggregation

EGW connects directly to the bank’s own PIS API aggregation layer. This allows banks to retain full control of API orchestration while leveraging EGW for merchant checkout integration.

Market availability is bank-determined

Partner API Aggregation

EGW integrates with external partners or fintechs who offer Open Banking aggregation as a service. This provides rapid expansion into new markets via partner coverage.

Markets determined by partner agreements

Custom Aggregation Solution(Optional)

Institutions may use Tietoevry’s standalone API aggregation platform as part of their internal stack to expose A2A capabilities to EGW.

Suitable for banks seeking full control with EGW front-end logic

Key Features of the Integration Framework

  • Standardized Interface to EGW - Regardless of aggregation model, EGW communicates via a common internal interface for initiating and tracking A2A payments, abstracting the underlying TPP logic.

  • Market Flexibility - Institutions can deploy a hybrid strategy — using Tietoevry’s aggregation in core markets while integrating with other banks or partners in extended regions.

  • Compliance Ready - Tietoevry acts as a licensed TPP for applicable markets, managing regulatory compliance, API security, and consent lifecycle management.

  • Authentication & Consent - All flows are based on Strong Customer Authentication (SCA) handled by the end-user’s bank, ensuring secure authorization under PSD2 requirements.

  • Plug-and-Play Checkout Integration - Open Banking A2A options are presented as part of the EGW Hosted Checkout Page, with automatic redirection to the selected bank for authorization.

Account-to-Account (A2A) Payments

The Tietoevry E-Commerce Payment Gateway supports native Account-to-Account (A2A) payment processing, allowing customers to pay directly from their bank accounts to merchant settlement accounts using trusted, regulated payment rails.

This payment method offers a low-cost, secure, and real-time alternative to card payments, and is particularly suited for regions with strong domestic transfer infrastructure (e.g., SEPA, TIPS, Nordic real-time rails).

How A2A Payments Work

A2A payments are initiated by the customer during checkout and completed via the customer’s online or mobile banking environment. The EGW facilitates the process by orchestrating the user flow, initiating the transfer, and providing real-time feedback to merchants.

A2A Checkout Flow:

  1. Customer selects “Pay by Bank” on the Hosted Checkout Page.

  2. Customer chooses their bank from a dynamic list.

  3. EGW redirects the customer to the selected bank’s authentication interface.

  4. Customer authenticates and authorizes payment via SCA.

  5. Funds are transferred to the merchant account.

  6. EGW receives payment confirmation and updates the merchant.

Supported A2A Schemes

Payment Rail
Description
Settlement Speed

SEPA Credit Transfer (SCT)

Standard Euro-denominated A2A transfer across the EU.

Same-day / Next-day

SEPA Instant Credit Transfer (SCT Inst)

Real-time A2A payments up to €100,000 (or scheme limit).

Under 10 seconds

TIPS

TARGET Instant Payment Settlement system by ECB.

Real-time

Domestic A2A Rails

National instant or batch-based clearing systems (e.g., Sweden’s Swish, Norway’s NICS, Baltics’ domestic rails).

Varies by country

Customer Experience

  • Integrated natively in the Hosted Checkout Page alongside card and wallet options.

  • Mobile-optimized with dynamic bank selection.

  • Secure redirect to bank interface for login and authorization.

  • Auto-return to merchant after confirmation.

  • Real-time feedback and merchant notification.

Gateway Capabilities

  • Payment initiation routing or back-end payment hubs.

  • Bank list management with logos, metadata, and availability.

  • Webhook and API callbacks to notify merchants of transaction status.

  • Fallback logic (e.g., from SEPA Instant to SCT if thresholds or limits are exceeded).

  • Support for refund as separate outbound payout transaction.

Last updated

Was this helpful?