LogoLogo
BlogLogin
English
English
  • An Introduction to Saferpay
    • Licensing
      • Legacy licensing
    • Reconciliation
    • Acquirers & Payment Methods
    • Web Shop Plugins and certified partners
      • ePages Beyond
      • ePages NOW
      • Magento 2
      • Odoo
      • PrestaShop
        • PrestaShop User Guide
      • Salesforce Commerce Cloud
      • SAP Commerce Cloud
      • Shopware 6
        • Shopware 6 User Guide - German
        • Shopware 6 User Guide - English
      • WordPress WooCommerce
      • Shopify
    • Supported Languages
    • Common Saferpay terms - Glossary
  • News
    • Changes for transactions without customer presence
    • Changes for the Saferpay Hosted Forms, Fields and Payment Page
  • Quick Links
    • Web Shop Plugins and certified partners
    • Secure PayGate
    • User Administration
    • Payment Page Configuration
    • Risk Management
    • API Authentication
  • Interfaces
    • Payment API (aka JSON API)
    • Management API
    • Backoffice
      • The Home screen
      • Batch Processing
      • Transactions
        • Transaction Details
        • Batch Close
        • Declined transactions
        • Pending authorizations
        • Analytics
        • SEPA Refunds Export
        • Authorization & Payment
        • Credit
      • Risk Management
      • Secure PayGate / Payment Links
      • Secure Card Data
        • Secure Card Data Details
      • Settings
        • JSON API basic/Client Certificate authentication
        • User Administration
        • Payment Page Configuration
      • Online Support
      • User Profile
    • Saferpay OnSite
    • Feedback
  • Integration Guide
    • Integrating Saferpay
    • Ways of integration
      • General Information
        • Data Security and PCI DSS
        • Versioning
        • 3-D Secure
        • PSD2
        • Dynamic Currency Conversion
        • Iframe Integration and CSS
        • Fraud Intelligence
          • Silver
          • Fraud Intelligence Integration
      • Payment Page
        • Payment Page checklist
      • Transaction Interface
        • Recurring Payments
        • Refunds
          • SEPA Refunds
      • Capture and Daily Closing
        • Partial Captures
          • Marketplace
      • Secure Card Data - Tokenization
      • Saferpay Fields
      • Inquire Interfaces
      • Mobile Integration
      • Omni-Channel
      • Mail Phone Order
      • Error Handling
      • API Health Check
      • Saferpay API Specification
    • Payment Methods & Wallets
      • General and special cases
      • Account-to-Account Payments
      • Alipay+
      • Apple Pay
      • American Express
      • Bancontact
      • Billie
      • blik
      • Click to Pay
      • Diners Club International & Discover Card
      • eps
      • giropay
      • Google Pay
      • iDEAL 2.0
      • JCB
      • Klarna Payments
      • Maestro International
      • Mastercard
      • paydirekt
      • PayPal
      • PostFinance Pay
      • Przelewy24
      • Reka
      • SEPA Direct Debit
      • Sofort by Klarna
      • TWINT
      • UnionPay
      • Visa & V PAY
      • WeChat Pay
      • WL Crypto Payments
    • Testing
    • Go-Live
    • Frequently Asked Questions
    • Saferpay Demo
      • Saferpay Demo Environment
      • Saferpay Demo Shop
    • Support
    • Changelog
Powered by GitBook
On this page
  • General requirements
  • Technical requirements
  • Supported features
  • Handling "PENDING" transactions
  • Forcing Instant payments
  • Inside the Saferpay Backoffice
  • Testing

Was this helpful?

  1. Integration Guide
  2. Payment Methods & Wallets

Account-to-Account Payments

PreviousGeneral and special casesNextAlipay+

Last updated 4 months ago

Was this helpful?

Account-to-Account Payments (bank transfer) is a new Worldline payment method. Transactions can be processed via the Saferpay JSON API. However, as also third party provider MSP and banks are involved in the process, there are a few things to consider.

General requirements

The handling of Account-to-Account Payments with Saferpay requires:

  • A corresponding license and thus a valid identification with a username and password for the Saferpay system.

  • At least one active Saferpay terminal on which the payment can be carried out. This could be a Saferpay Payment Page or a Saferpay Secure PayGate terminal.

  • A valid Account-To-Account acquiring contract

The Account-to-Account transaction is approved and payment is guaranteed once funds are transferred to the Worldline account. Until that moment, the transaction remains in the pending status. In the case of real-time payment (SCT Inst.), the transaction is expected to be processed within several seconds. For other payments - up to 3-4 days. The transaction is expired if no status is received within the next 120 hours.

You can monitor the status on the "Pending Authorizations" page in the Backoffice:

Technical requirements

The general integration of Account-to-Account Payments can only be done via the and requires the following things to be noted:

  • As banks do not allow Iframe integration, Saferpay will break out of the Iframe, so the payment may be performed, using a full-size payment page.

  • JSON API integration is only possible with the API version 1.38 or higher.

  • Refund:

    • A refund cannot be cancelled, so make sure that you really want to execute it. The refund amount may be less than or equal to the original payment amount. Depending on the bank, it may take several days for the refund to be processed and paid out.

    • Note that the CaptureId, needed for a refund, is returned as part of the response of .

    • Parameter PaymentMethodsOptions.A2A.AccountHolderName: The account holder name will be used if not already present in the authorization. If no account holder name is present in the authorization and none provided in the refund request, the refund cannot be processed.

  • The parameters OrderId and PayerNote are limited to 50 characters.

  • The notification URLs, inside theNotification container are mandatory, in order to avoid missing payment successes and also to . See the for further information.

  • At checkout, the payment method could be described as follows: "Pay straight from your bank account through your online banking. It's simple, secure and certified by European regulatory authorities."

Supported features

Feature

Support

❌/❌

Multipart Captures

❌

Secure Card Data

❌

✅

Recurring Payments

❌

3D Secure

❌

Dynamic Currency Conversion (DCC)

❌

Mail Phone Order

❌

✅

Secure PayGate

✅

Handling "PENDING" transactions

This status means, that the final transaction status could not be determined in due time. This is due to some banks needing additional processing time, which can be up to 120 hours.

If a PENDING status is recieved, the merchant should display a message to the payer, telling them, that the payment is still in progress at their bank and that they'll be notified about the outcome, once it is received.

Once the outcome is processed, the merchant should notify their customer about the outcome, be it positive, or negative.

Forcing Instant payments

Saferpay offers an option, to enable "Instant Payments" for the merchant account, cutting down on the PENDING transactions and also the waiting time, should a PENDING status still occour.

This option is optional and has to be activated on the merchant account, if desired.

Some banks do not support instant payments. Activating this option on your account, will lead to some banks not being displayed for the payer and thusly will prevent some customers from being able to pay via Account-to-Account Payments.

Inside the Saferpay Backoffice

Testing

Capture/

Account-to-Account Payments introduces a new status, that can be returned with the , being PENDING.

The merchant system will be notified via , that have been defined with the . If the notification is received, the merchant system should execute the , in order to ask for the transaction outcome.

PENDING transactions are handled within , to give you an overview of payments, that are still in progress.

Please refer to , if you want to test Account-to-Account Payments.

a special section of the Saferpay Backoffice
this chapter
Refunds
Needs attention!
Testing
Payment Page
Payment Page Assert
handle PENDING transactions
Cancel
Payment Page process
Payment Page Assert
the Notification URLs
Payment Page Initialize request
Payment Page Assert