It is a tool for companies to manage SEPA direct debits (the new name for payment receipts or direct debits).
Yes, you will need to register with your bank the fact that you will be issuing SEPA direct debits through at least one of the two possible schemes: CORE and B2B.
You can collect your SEPA direct debits in all countries that are regulated by SEPA. These include the 28 countries that make up the EU as well as Iceland, Liechtenstein, Monaco, Norway and Switzerland.
No, clients do not need to give us access to online banking.
If you need more information or additional assistance you can reach us at email@example.com or through the form on our contact page.
Yes, before making SEPA direct debits in an account, the entity will seek the authorisation of the debtor.
To issue SEPA direct debits with us you should use your own bank and contract if it is one of the banks we already work with (see the list in More information).
With Besepa you can issue through two different types of schemes:
In Spain not all entities support the different SEPA direct debit schemes, especially when it comes to COR1 and B2B.
Here is a list of Spanish entities and the different schemes they each support.
To delete all the data in the Besepa sandbox, go to the top right side of the screen, click on your data and go to developers. There you will find the Clear test data button.
Yes, but not only with Besepa, with any type of company, service, or institution, if you are going to give their information to process payments, for marketing purposes, etc., you should get authorisation.
You can do it using our API, or, if you prefer, an Excel/SVC/etc., and we can help you. Although it would be great if you could do it yourself, if not done properly, the chances of mandates being invalidated is much higher, so we prefer to walk you through it.
You have all the necessary information on the Besepa API here. If you need additional support, contact us at firstname.lastname@example.org and we will help you with whatever you need.
Assuming you already have your client information, or are going to obtain it, creating a client in Besepa is pretty simple.
The first step is to determine if you want to create only the client, or the client + bank account and mandate. There are situations in which both scenarios make sense.
To create a client we will make a call to the endpoint/api/1/customers of the environment, indicating the client’s information according to the API documentation.
Yes, Besepa works as an OAuth provider and can be used to authorise the use of our API by third parties.
We have different URLs for testing/sandbox environments and production environments:
– Sandbox: https://sandbox.besepa.com
– Production: https://api.besepa.com
The process to create a subscription by API integrated in your site is as follows:
1º Request registration information from your client.
2º Make a call to our API to create the client + bank account with mandate.
3º If you use our mandate signature, in our response to the previous call you will have the mandate signature URL, which you will have to redirect to the client. If you gave us the mandate information in the previous call, you don’t have to do anything here.
4º Once you receive confirmation of the signature in the webhook that you have declared in your account, you can create the subscription: http://docs.besepa.apiary.io/#reference/suscripciones/subscriptions/crear-una-subscription
Charges and Transactions
A charge is “an intention to collect” from a client, something like an invoice, while a transaction is each collection attempt made.
A charge can be canceled up to the time it is sent to the bank.
If I cancel a transaction, that particular collection attempt has been cancelled, but that does not necessarily mean that you want to cancel the “debt” (the charge) that the client has.
Unfortunately that is how direct debit works, but it doesn’t work like that in the world of cards.
When a charge is sent for collection on date x, that charge will always be paid by the bank on date x and you will have the money in your account (whether or not it is available is another matter). What can happen is that within a few days that money is retracted, because in reality that charge could not be collected.
Managing the mandate
Through Besepa, digital signature with OTP is used to prepare the SEPA mandate.
Yes, you can register SEPA mandates that you already have from clients, or new ones that you got on paper, when adding the client account. You simply have to indicate that you have their bank information and enter the scheme (CORE / B2B), reference, and date of signature.
Yes, mandates expire 36 months after their last use (regardless of whether it was paid, rejected, returned or refunded).
No, you don’t have to sign another mandate. However, it is mandatory that the change request be recorded because in the event of a dispute, your client’s bank can ask you for both the mandate and the account change request.
A new mandate should be issued for SEPA direct debits in the following situations:
– Changing from Core to B2B, or vice versa
– If the debtor has changed (this involves a new signature)
– If the mandate has expired
To send the URL where your client can access the mandate to sign you must first go into the account details. Once there, copy the URL of the mandate and send it to your client however you like.
Definitely, you just have to indicate that the charge is recurring, and indicate how often it will be charged.
Yes, no problem. In the product information there is a URL you can use for your clients to subscribe directly