Method of subscribing to a bank direct debit mandate using a blockchain

Abstract

The invention relates to a method for enabling a user (1) to subscribe to a bank direct debit mandate with a creditor organization (2) by means of a blockchain, said method providing for: the creation of at least one digital vault (5) linked to a paid service offered by the creditor organization (2); the communication to said creditor organization of a digital access address to said digital vault in the blockchain; when the user (1) subscribes to a paid service offered by the creditor organization (2), to: communicate to said user a notification (7) including at least one digital access address to the digital vault (5) corresponding to said service in the blockchain, in order to enable the user (1) to interact with said digital vault to create and / or modify said mandate;to store information (G) in the digital vault (5) to allow the user (1) and / or the creditor organization (2) to view the mandate created and / or modified. Figure 1;

Description

Title of the invention: Method for subscribing to a bank direct debit mandate using a blockchain

[0001] The invention relates to a method for enabling a user to subscribe to a bank direct debit mandate with a creditor organization by means of a blockchain, as well as an architecture for implementing such a method.

[0002] It applies in particular to the creation and management of bank direct debit mandates between a public or private body, such as for example an energy supplier, a landlord or a public administration, and users who have to make regular payments to such a body, for example to pay rent, a subscription to a service or taxes.

[0003] In Europe, bank direct debit mandates are established according to directives specific to the Single Euro Payments Area (SEPA) for member states, including France.

[0004] According to these guidelines, in order to establish such a mandate, the creditor organization must first have its debtor sign an agreement, who may contest a bank withdrawal in the absence of such a signature.

[0005] Each mandate must include a unique identifier, called the Unique Mandate Reference (UMR), as well as an identifier for the creditor organization, the SEPA Creditor Identifier (ICS). Furthermore, there are two types of mandates:

[0006] - the single direct debit mandate, for which the RUM reference will only be used once; and - the recurring direct debit mandate, for which the RUM reference will remain the same throughout the entire life of said mandate.

[0007] To implement such a mandate, the creditor organization may prepare paper forms for the debtor to complete and sign manually. Alternatively, an electronic form may be created, and the debtor may be sent an electronic message, such as an email or SMS (Short Message Service), to enable the debtor to electronically sign the mandate.

[0008] In addition, some banks offer creditor organizations services for managing their bank direct debit mandates, which also allows said banks to facilitate cash flow controls.

[0009] Existing solutions do not provide complete satisfaction, either for creditor organizations or for debtors.

[0010] Indeed, for creditors, the operational management of mandates (signing, (preservation, updating...) is difficult to implement in practice.

[0011] For debtors, particularly individuals, the main difficulty stems from the multiplicity of solutions. Indeed, since an individual has on average five regular creditors, and each of these creditors manages their mandates differently, notably via their own IT platform, this requires the individual to create as many different accounts and passwords. Furthermore, when an individual wishes to cancel their subscription to a service, revoking the corresponding mandate is difficult to do.

[0012] In addition, existing solutions offer few possibilities to allow banks to consult and / or verify the status of mandates corresponding to a given direct debit, so that said banks cannot, for example, warn their customers if a bank debit continues to be made when the corresponding mandate has been revoked.

[0013] The invention aims to improve the prior art by proposing in particular a method enabling a user to easily create and manage bank direct debit mandates with a creditor organization, said method further providing for facilitating the consultation of said mandates by said user, said creditor organization and their respective banks.

[0014] To this end, according to a first aspect, the invention proposes a method for enabling a user to subscribe to a direct debit mandate with a creditor organization by means of a blockchain, said method providing for:

[0015] - the creation of at least one digital safe linked to a paid service offered by the creditor organization; - the communication to the creditor organization of a digital access address to the digital vault in the blockchain;

[0016] said process further providing, when the user subscribes to a paid service offered by the creditor organization, for:

[0017] - communicate to said user a notification including at least one digital access address to the digital vault corresponding to said service in the blockchain, in order to allow the user to interact with said digital vault to create and / or modify said mandate; - to record information in the digital vault to allow the user and / or the creditor organization to consult the mandate created and / or modified.

[0018] According to a second aspect, the invention proposes an architecture for enabling a user to subscribe to a direct debit mandate with a creditor organization by means of a blockchain, said architecture comprising:

[0019] - at least one platform for providing a digital vault service on the blockchain, said platform comprising: • means to enable a creditor organization to create at least one digital vault linked to a paid service offered by said organization; • means to communicate to the creditor organization a digital access address to the digital vault in the blockchain; • means to, when the user subscribes to a paid service offered by the creditor organization, communicate to said user a notification including at least one digital address for accessing the digital vault corresponding to said service in the blockchain; - a terminal comprising: • means to receive the notification communicated by the platform; • means to allow the user to interact with said digital vault using the digital address provided with the notification, in order to create and / or modify said mandate;

[0020] said platform and said terminal further comprising means for recording in the digital vault information to allow the user and / or the creditor organization to consult the mandate created and / or modified.

[0021] Other features and advantages of the invention will become apparent from the following description, made with reference to the accompanying figures, in which:

[0022] - Figure 1 schematically represents the steps of creating and modifying a bank direct debit mandate between a user and a creditor organization of a process according to an embodiment of the invention; - Figure 2 schematically represents another step in modifying the mandate of the process in Figure 1; - Figure 3 schematically represents another way of carrying out the steps in Figure 1; - Figure 4 schematically represents a tree of digital fingerprints of a bank direct debit mandate obtained from different hash functions, and their link to allow a given organization to retrieve the digital fingerprint recorded in the digital vault.

[0023] In relation to these figures, a method for enabling a user is described below. lancier 1 to subscribe to a bank direct debit mandate with a creditor organization 2 by means of a blockchain, as well as an architecture for the implementation of such a process.

[0024] User 1 may in particular be a particular user equipped with a terminal 3, for example a mobile terminal such as a smartphone, tablet or personal digital assistant (PDA), or a fixed terminal such as a desktop computer.

[0025] The creditor entity 2 may be a public institution, for example a state administration, or a private institution, for example a supplier of electricity, water or gas, or a supplier of a fixed or mobile telephone service.

[0026] The process first involves creating at least one digital safe 5 linked to a paid service offered by the creditor organization 2, then communicating to said creditor organization a digital address for accessing said digital safe in the blockchain.

[0027] To this end, the architecture includes at least one platform 6 for providing a digital vault service on the blockchain, said platform including:

[0028] - means to enable a creditor organization 2 to create at least one digital vault 5 linked to a paid service offered by said organization; - means to communicate to said creditor organization a digital access address to said digital vault in the blockchain.

[0029] The platform 6 may for example include means for providing a suitable programming interface (API, for the English Application Programming Interface), said interface being arranged to allow an operator to create for the creditor organization 2 a digital vault 5 adapted to a given paid service provided by said organization.

[0030] The operator may be, for example, an employee working directly for the creditor organization 2, or for a third-party organization managing the creation of bank direct debit mandates for said organization on the blockchain.

[0031] The digital vault 5 can for example be created in the form of a computer protocol of the smart contract type, said smart contract being accessible by means of a public digital address on the blockchain.

[0032] The digital vault 5 contains data that will be common to all subsequent direct debit mandates created for the corresponding service, thus ensuring the permanence of this data and saving time when creating such mandates. This data includes, in particular:

[0033] - an identifier of the creditor organization 2, including its name, its identifier ICS, and possibly a logo; - at least one digital address of the entity(ies) that created said digital vault on the blockchain, for example the creditor organization 2 itself and / or an operator of a third-party organization working for said creditor organization; - possibly, an identifier of the operator and / or third-party organization that created said digital safe for the creditor organization 2; - the wording of the paid service linked to said digital safe; - the type of mandate, for example a SEPA mandate; - the type of sample taken, for example recurring or one-time.

[0034] When a user 1 subscribes to a paid service offered by the financial institution 2, the process provides for communicating to said user a notification 7 including at least one digital address for accessing the digital vault 5 corresponding to said service in the blockchain, in order to allow the user to interact with said digital vault to create and / or modify a bank direct debit mandate.

[0035] To do this, the platform 6 includes means for sending such a notification 7 to the user 1, for example in the form of an electronic message readable by the terminal 3 of the user 1, such as an email or an electronic message of type SMS or MMS (for English Multimedia Messaging Service).

[0036] The notification 7 may include an interactive link 8, for example in the form of a QR (Quick Response) type barcode, which is linked to the address of the digital vault 5 on the blockchain, in order to allow the user 1 to access said digital vault by interacting with said link.

[0037] To enable user 1 to interact with the platform 6 and / or the digital safe 5, the terminal 3 of said user includes means for receiving the notification 7 communicated by the platform 6, as well as means for enabling the user to interact with the digital safe 5 in order to create and / or modify a bank direct debit mandate with the creditor organization 2, in particular by interaction of said terminal with the link 8 contained in said notification.

[0038] In particular, the architecture may include an application 4 equipped with such means, which the user 1 can download onto his terminal 3, in particular by sending a request 9 adapted to said platform.

[0039] In relation to Figures 1 and 3, application 4 comprises:

[0040] - means for obtaining information on the bank details of user 1, for example the IB AN (International Bank Account Number) of a bank account of said user, in particular by capturing an image of a Bank Account Statement (RIB) 10 provided by said user user ; - means to send to platform 6, for example via a suitable API interface, a notification 11 containing said bank details and / or said image capture.

[0041] After receiving the notification 11, the platform 6 verifies the bank details it contains, in particular by interaction between an adapted interface 12 and a database 13 in which such details are recorded, for example a database of an international platform listing all the IB AN numbers of a given geographical region.

[0042] Following this verification, the platform 6 sends the application 4 an appropriate notification 14, in particular to confirm the success or failure of said verification.

[0043] In parallel, user 1 identifies himself to the platform 6, for example by means of a pair of private and public keys assigned to said user on the blockchain.

[0044] The keys are linked to user 1's terminal 3 and can be created directly in said terminal under the control of said user, who only uses the public key to interact with the blockchain and the rest of the system. Therefore, the private key never leaves user 1's terminal 3, thus ensuring optimal security for said user.

[0045] To do this, the terminal 3 may include means, in particular integrated into an application installed on said terminal, to enable user 1 to create or come into possession of such a key pair under the control of said user.

[0046] In relation to [fig.1], if user 1 already has such a key pair at the time of the creation of the bank direct debit mandate, his public key is recorded in a specific digital vault 15 of the blockchain.

[0047] In particular, this public key can be registered therein by being associated with a digital identity of the user 1 independent of the blockchain, for example his credentials on a third-party platform 16 of another online service, which allows said user to connect to the blockchain by means of these credentials, if necessary avoiding the use of said public key.

[0048] Thus, to identify himself, the user 1 sends, for example by means of the application 4, a request 17 with his identifiers to the corresponding third-party platform 16, which responds to said user by sending him a notification 19 of success or failure of identification, depending on whether the identifiers communicated correspond or not to an identity recognized by the service attached to said third-party platform.

[0049] As a result, if this identification is successful, the third-party platform 16 sends a notification 18 via the platform 6 to a vault 15 as described above to position the public key of user 1 on the blockchain, said vault 15 being either created at that time, or reused if one already existed for said user on the blockchain.

[0050] Furthermore, after identification of user 1, the process provides for recording in the vault 15 the bank details communicated by said user, in particular by sending an adapted request 32, associating them with his public key on the blockchain and with his identifiers on the third-party platform 16.

[0051] In relation to [fig.3], if user 1 does not yet have access keys to the blockchain at the time of the creation of the mandate, the process provides for the creation of such keys prior to the creation of said mandate.

[0052] To do this, user 1 creates a key pair, then sends a request 20 to platform 6, using application 4, containing their public key and their credentials on a third-party platform 16. Platform 6 interacts with said third-party platform to identify the user. Next, platform 6 interacts with the vault 15 to store the public key thus created, associating it with user 1's credentials on the third-party platform 16 and with the bank details provided in notification 11.

[0053] The method then involves recording information in the digital vault 5 to allow the user 1 and / or the financial institution 2 to consult the created and / or modified mandate. To this end, the platform 6 and the application 4 include means for performing such recording.

[0054] To finalize the creation of the direct debit mandate, user 1 connects to the application 4, for example by entering his bank details, and possibly a password to protect the storage of said bank details, so that said application sends a request 21 containing information on said mandate to the digital vault 5.

[0055] Next, the application 4 displays on the terminal 3 information on the mandate, which combines in particular the information pre-recorded in the digital safe 5 (identifiers of the creditor organization 2, type of service, type of withdrawal...) and the information previously communicated by said user to the platform 6 (public key, identifiers on the third-party platform 16, IB AN number...).

[0056] In parallel, as shown in [fig.3], user 1 can send a request 24 to a platform 22 of a banking institution 23 of the creditor organization 2, in order to consult other information relating to said banking institution, for example the general terms and conditions of transactions in force in said banking institution.

[0057] The information recorded in the digital vault 5 may include a digital identifier of the mandate, for example a Unique Mandate Reference (UMR), said identifier comprising a first alphanumeric sequence linked to the vault- a strong numeric 5 and a second alphanumeric sequence linked to a user identifier 1 on the blockchain, including their public key for accessing said blockchain.

[0058] According to one embodiment, the RUM digital identifier includes a third alphanumeric sequence linked to a mandate status, the method providing for modifying said third alphanumeric sequence when user 1 and / or creditor organization 2 modifies said status. To this end, application 4 and platform 6 include means for carrying out this modification.

[0059] Advantageously, the information stored in the digital vault 5 includes at least one digital fingerprint G of the mandate (for the English term, "hash"), the user and / or the creditor organization 2 accessing said mandate by interacting with said digital fingerprint, in particular by means of a suitable hashing function. To this end, the application 4 and the platform 6 include suitable means for calculating and storing such a digital fingerprint G in the vault 5, in particular by sending said application a request 21 containing said fingerprint G.

[0060] Thus, we avoid recording the mandate in its entirety in the digital safe 5, which makes it possible to limit the volume of data recorded in said safe, but also to guarantee a certain confidentiality to the user 1.

[0061] In particular, the application 4 and the platform 6 can be arranged to display the mandate information in a format readable by a human operator or user 1, in particular in the form of a .jpeg or .pdf file containing the said information in text.

[0062] User 1 and / or creditor organization 2 may also provide an agreement to their respective banking institutions to allow them to access the mandate information, in particular by communicating at least a digital fingerprint and / or additional information from said mandate, which said banking institutions may use in combination with other information provided by their client to access said authorized information from said mandate.

[0063] In relation to [fig. 4], the creditor entity 2 can communicate to its bank:

[0064] - a digital fingerprint E of the mandate, obtained from a given hash function; and - the digital address of safe 5.

[0065] Furthermore, the bank can calculate successively:

[0066] - a digital fingerprint F, from another hash function and data Fl containing the mandate RUM identifier and the ICS identifier present in the bank direct debit flow of said organization; and - the G fingerprint recorded in safe 5, from this F fingerprint and of the E footprint communicated by the said body.

[0067] Similarly, user 1 can communicate with their bank:

[0068] - a digital fingerprint C of the warrant, which can be obtained by concatenation and hashing of: • a fingerprint A, obtained by a hash function of the metadata A1 of the warrant, which corresponds to a computer-readable part of said warrant; and • a fingerprint B, obtained by hashing the metadata A1 of the warrant and a screenshot B1 of a human-readable file of said warrant;

[0069] - the digital address of safe 5; and - a salting fingerprint of the mandate data, obtained using a suitable cryptographic function.

[0070] In particular, the bank of user 1 can calculate the G fingerprint recorded in the safe 5 by calculating:

[0071] - a D imprint of the mandate from the salt imprint and DI data already in its possession, including the name and surname of said user and the IB AN number of his account in said bank; - an E impression from impressions C and D; and - an F impression as described previously.

[0072] After receiving the request 21, the platform 6 and / or the application 4 can in particular record a digital fingerprint G and a digital identifier RUM as presented above in the digital vault 5, in particular by sending a notification 25 adapted to the vault 15 of user identification of the user 1, which then interacts with the vault 5 of the service to which said user has subscribed ( [fig.3]), the third alphanumeric sequence of said RUM identifier indicating that the status of the mandate is “reserved” or “pending signature”.

[0073] The method provides for enabling user 1 to interact with the digital safe 5 to electronically sign the mandate, in order to validate acceptance of payment by direct debit of the service to which said user has subscribed by means of said mandate.

[0074] To do this, the terminal 3 includes suitable means, in particular integrated into the application 4 described above, which are arranged in particular to display on the terminal 3 an interactive link, for example in the form of a button, with which the user 1 can interact, for example by digital contact with the touch screen of said terminal, to send a request 26 for electronic signature of the mandate to the safe 5.

[0075] In particular, with the sending of this request 26, the application 4 records in the safe 5:

[0076] - at least one modified digital fingerprint G of the mandate, in order to notify its electronic signature by user 1 in the read format accessible by said fingerprint; - a modified RUM numeric identifier of said mandate, in which the third alphanumeric sequence has been modified to indicate a "signed" status for said mandate.

[0077] The method also provides for enabling user 1 to interact with the digital vault 5 to revoke the mandate, in order to interrupt payment for the service to which said user subscribed by means of said mandate.

[0078] In relation to [fig.2], the application 4 includes for this purpose suitable means, for example to display on the terminal 3 an interactive button which the user 1 must activate to request the revocation of the mandate, in particular by sending a request 27 adapted to the digital safe 5.

[0079] Thus, the application 4 records in the digital vault 5 a new digital fingerprint G to notify this revocation in the mandate reading formats accessible by said fingerprint, as well as a new digital identifier RUM whose third alphanumeric sequence has been modified to indicate a status "revoked by the debtor".

[0080] Similarly, when the mandate is revoked by the creditor body 2, in particular via the platform 6, said platform can register in the digital vault 5 a new adapted digital fingerprint G, as well as a new digital identifier RUM whose third alphanumeric sequence has been modified to indicate a status "revoked by the creditor".

[0081] In relation to [fig.3], user 1 can in particular download a .jpeg or .pdf file containing information on the mandate and a notification of its signature or revocation, and send to a platform 22 of the banking institution 23 a notification 29 including this file, in order to be able to carry out additional checks.

[0082] As shown in Figures 1 and 2, the process also provides, in particular through adapted means of the application 4, for sending a notification 28 to the creditor organization 2 when the user creates and / or modifies the mandate, in particular to sign it electronically ([fig.1]) or revoke it ([fig.2]), in order to request validation of said creation and / or modification by said organization before recording the information of said mandate in the digital vault 5.

[0083] In particular, the creditor organization 2 sends to the vault 5 a notification 30 to validate the modification, then a notification 31 to the application 4 to inform the user 1 of said validation.

Claims

Claims

1. Method for enabling a user (1) to subscribe to a direct debit mandate with a creditor organization (2) by means of a blockchain, said method providing: - the creation of at least one digital safe (5) linked to a paid service offered by the creditor organization (2); - the communication to said creditor organization of a digital access address to said digital safe in the blockchain; said method further providing, upon subscription of the user (1) to a paid service offered by the creditor organization (2), to: - communicate to said user a notification (7) comprising at least one digital access address to the digital safe (5) corresponding to said service in the blockchain, in order to enable the user (1) to interact with said digital safe to create and / or modify said mandate;- record in the digital safe (5) information (G) to allow the user (1) and / or the creditor organization (2) to consult the mandate created and / or modified.;

2. Method according to claim 1, characterized in that it provides for communicating to the user (1) a notification (7) comprising an interactive link (8) linked to the digital address of the digital safe (5), in order to allow the user (1) to access said digital safe by interaction with said link.

3. Method according to one of claims 1 or 2, characterized in that it provides for allowing the user (1) to interact with the digital safe (5) to electronically sign the mandate, in order to validate the acceptance of the payment by bank debit of the service to which said user has subscribed by means of said mandate.

4. Method according to any one of claims 1 to 3, characterized in that it provides for allowing the user (1) to interact with the digital safe (5) to revoke the mandate, in order to interrupt the payment by bank debit of the service to which said user has subscribed by means of said mandate.

5. Method according to any one of claims 1 to 4, characterized in that it provides for sending a notification (28) to the creditor organization (2) when the user (1) creates and / or modifies the mandate, in order to request validation of said creation and / or modification by said organization before recording the information (G) of said mandate in the digital safe (5).

6. Method according to any one of claims 1 to 5, characterized in that the information recorded in the digital safe (5) comprises a digital identifier of the mandate, said identifier comprising a first alphanumeric sequence linked to said digital safe (5) and a second alphanumeric sequence linked to an identifier of the user (1) on the blockchain.

7. Method according to claim 6, characterized in that the digital identifier comprises a third alphanumeric sequence linked to a status of the mandate, said method providing for modifying said third alphanumeric sequence when the user (1) and / or the creditor organization (2) modifies said status.

8. Method according to any one of claims 1 to 7, characterized in that the information recorded in the digital safe (5) comprises at least one digital fingerprint (G) of the mandate, the user (1) and / or the creditor organization (2) accessing said mandate by interaction with said digital fingerprint.

9. Architecture for enabling a user (1) to subscribe to a direct debit mandate with a creditor organization (2) by means of a blockchain, said architecture comprising: - at least one platform (6) for providing a digital safe service on the blockchain, said platform comprising: • means for enabling a creditor organization (2) to create at least one digital safe (5) linked to a paid service offered by said organization; • means for communicating to said creditor organization a digital access address to said digital safe in the blockchain; • means for, when the user (1) subscribes to a paid service offered by the creditor organization '2), communicating to said user liser a notification (7) comprising at least one digital access address to the digital safe (5) corresponding to said service in the blockchain; - a terminal (3) comprising: • means for receiving the notification (7) communicated by the platform (6); • means for allowing the user (1) to interact with said digital safe by means of the digital address communicated with the notification (7), in order to create and / or modify said mandate; said platform and said terminal further comprising means for recording in the digital safe (5) information (G) to allow the user (1) and / or the creditor organization (2) to consult the created and / or modified mandate.

10. Architecture according to claim 9, characterized in that the platform (6) comprises means for communicating to the user (1) a notification (7) comprising an interactive link (8) linked to the digital address of the digital safe (5), in order to allow the user (1) to access said digital safe by interaction of the terminal (3) with said link.

11. Architecture according to one of claims 9 or 10, characterized in that the terminal (3) comprises means for allowing the user (1) to interact with the digital safe (5) to electronically sign the mandate, in order to validate the acceptance of the payment by bank debit of the service to which said user has subscribed by means of said mandate.

12. Architecture according to any one of claims 9 to 11, characterized in that the terminal (3) comprises means for allowing the user (1) to interact with the digital safe (5) to revoke the mandate, in order to interrupt the payment by bank debit of the service to which said user has subscribed by means of said mandate.

13. Architecture according to any one of claims 9 to 12, characterized in that the terminal (3) comprises means for sending a notification (28) to the creditor organization (2) when the user (2) creates and / or modifies the mandate, in order to require validation of said creation and / or modification by said organization before recording the information (G) of said modified mandate in the digital safe (5).

14. Architecture according to any one of claims 9 to 13, characterized in that the terminal (3) and the platform (6) comprise means for recording a digital identifier of the mandate in the digital safe (5) during the creation and / or modification of said mandate, said identifier comprising a first alphanumeric sequence linked to said digital safe and a second alphanumeric sequence linked to an identifier of the user (1) on the blockchain.

15. Architecture according to one of claims 13 or 14, characterized in that the digital identifier comprises a third alphanumeric sequence linked to a status of the mandate, the terminal (3) and the platform (6) comprising means arranged to modify said third alphanumeric sequence when the user (1) and / or the creditor organization (2) modifies said status.

16. Architecture according to any one of claims 9 to 15, characterized in that the terminal (3) and the platform (6) comprise means for recording in the digital safe (5) at least one digital fingerprint (G) of the mandate during its creation and / or modification, the user (1) and / or the creditor organization (2) accessing said mandate by interaction with said digital fingerprint.

Images