SEPA preview build available

Discussion in 'News & Announcements' started by FedorK, Jan 16, 2014.

  1. FedorK

    FedorK Mega Poster

    The Single Euro Payments Area (SEPA) stands for the European Union (EU) payments integration initiative.

    PBAS will support SEPA starting with 4.5.1 version.
    For the SEPA scheme, we have developed the new Bank Transfer plugin, expanded the PBAS functionality and API.

    How the SEPA Direct Debit scheme is implemented in PBAS:

    For the first payment the signed mandate is provided (I) and then the transaction is processed in a usual way (II):

    I. Making first payment with SEPA and providing the signed mandate.
    • The customer orders services and uses SEPA payment. The customer provides bank account details (Bank Code and Account Number (IBAN) ) and places the order. The Payment Method of the Bank Account type is created in PBAS with the status Unchecked.
    • PBAS automatically sends the notification to the customer with the mandate PDF form attached.
    • The customer signs the mandate and sends its signed copy to Provider.
    • Provider receives the signed mandate and then manually enters the mandate sign date for the customer's Bank Account and marks Customer's Bank Account as Verified.

    II. SEPA transactions processing.
    • The customer applies the SEPA Bank Account to the payables. PBAS automatically sends notification to the customer, telling that the payment will be collected using SEPA Direct Debit and the payment due date.
    • Provider generates the batch according to the SEPA SDD CORE rules. Then provider should manually send the batch to the bank. Provider's Bank processes the received Batch and requests Customer's Bank to make a transfer. Customer's Bank charges Customer's account and credits Provider's account. The bank generates the response batch, which contains the statuses of the SEPA payment transactions.
    • Provider receives the response batch and imports it to PBAS. PBAS automatically processes the batch, marking the failed payments and releasing the successful ones.

    All the notification templates are generated automatically during the SEPA plugin activation.
    The Printable form for the mandate PDF and e-mails are pre-configured. Provider may customize the default text.

    Provider also should fill the "Creditor Identifier" in the Printable form for the mandate PDF:
    Configuration Director > Miscellaneous Settings > Printable Forms > SEPA Mandate forms.

    The Plugin configuration has the following parameters:

    Bank Code - creditor’s (Provider’s) Bank Identifier Code (BIC, ISO 9362).
    Account Number - creditor’s (provider’s) International Bank Account Number (IBAN, ISO 13616)
    Due Period (calendar days) - the number of days before the customer’s account will be debited. The default is 14 days.
    Latest reception of first collection* (5 days) - The sufficient period of time before the scheduled due date, when the batch containing the first payments by Bank Account(s) should be sent to the bank.
    Latest reception of subsequent collection* (2 days) - – The sufficient period of time before the scheduled due date, when the batch containing the recurring collections should be sent to the bank.
    * * * You may configure these parameters according to your bank working schedule. If the batch was not sent to the bank in time, then the scheduled due date cannot be met by the bank, thus you should keep in mind that the transfer due date will be shifted in the batch to nearest working day accordingly.

    The Sign Date for each payment method is undefined. But it is still possible to use such payment methods in batches.

    You can download the PBAS 4.5.1 preview:
    Please install it only on staging node as clean install.

    RedHat/CentOS 5:

    RedHat/CentOS 6:

Share This Page