Bank Mobility
In the European banking landscape, particularly in France under the Macron Law, the BMN (Bank Mobility Notification) file is SlimPay messaging format used to notify the switching of debtors' bank accounts.
SlimPay simplifies this for merchants. If you are a merchant using SlimPay and your customer changes banks (either through bank mobility or bank merger):
- SlimPay receives the mobility information via the interbank network.
- Instead of you having to contact the customer for a new IBAN, SlimPay automatically updates the mandate in the system with the new banking details (an amendment is created).
- The next payment cycle simply triggers against the new IBAN using the existing mandate reference, preventing "R-transactions" (refusals) due to closed accounts.
- SlimPay communicates to merchants BMN files containing the information related to bank mobilities (once a day if there are mobilities during that day).
You will find below the format of the BMN file (.CSV) sent by SlimPay:
Header line
| Field | Name | Definition | Format | Size | Occurrence (when filled) | Comments |
|---|---|---|---|---|---|---|
| 1 | LineType | Type of the line | HEADER | [6,7] | Once per line | Information of the Event Report Export |
| 2 | FileName | Generated file name | String | 255 | Once per file | |
| 3 | ExportDate | Creation date of event report export | 2011-08-02 (ISO format) | 10 | Once per file |
Mandate line
| Field | Name | Definition | Format | Size | Occurrence (when filled) | Comments |
|---|---|---|---|---|---|---|
| 1 | Line Type | Type of the line | MANDATE | [6,7] | Once per line | Information of the Mandate |
| 2 | EventType | Type of event | SA_APPLIED, SA_NOT_APPLIED, REVOKED | [8,38] | Once per mandate | Indicates whether the modification was applied, already updated, or revoked |
| 3 | umr | Unique mandate reference | 35 | Once per mandate (35) | ||
| 4 | sci | Sepa Creditor Identifier | 28 | Once per mandate | ||
| 5 | subscriberReference | Subscriber reference | String | 35 | Once per mandate | |
| 6 | signatureDate | Signature date | 2011-08-02 (ISO format) | 16 | Once per mandate | |
| 7 | sequenceType | Mandate Sequence type | RCUR or OOFF | 4 | Once per mandate | |
| 8 | mandateType | Mandate scheme | CORE (B2C) or B2B | [3,4] | Once per mandate | |
| 9 | status | Status | ACTIVE, REVOKED | [6,22] | Once per mandate | |
| 10 | OriginalDebtorName | Original debtor name | String | 70 | Once per mandate | |
| 11 | OriginalDebtorBic | Original debtor BIC | BIC Format | 11 | Once per mandate | |
| 12 | OriginalDebtorIban | Original debtor IBAN | IBAN Format | 34 | Once per mandate | |
| 13 | NewDebtorName | New debtor name | String | 70 | Once per mandate | |
| 14 | NewDebtorBic | New debtor BIC | BIC Format | 11 | Once per mandate | |
| 15 | NewDebtorIban | New debtor IBAN | IBAN Format | 34 | Once per mandate | |
| 16 | Reference | Reference of the switching account request | String | 35 | Once per mandate | |
| 17 | SignatureDate | Signature date of the switching account | 2011-08-02 (ISO format) | 16 | Once per mandate | |
| 18 | SwitchingOrigin | Origin of the bank account switch | MERCHANT, BANK, ACCOUNT SWITCHING REQUEST, BANK MERGER | 8,30 | Once per mandate | Indicates the origin of the switching request |
Footer line
| Field | Name | Definition | Format | Size | Occurrence (when filled) | Comments |
|---|---|---|---|---|---|---|
| 1 | Line Type | Type of the line | FOOTER | 6,7] | Once per line | Summary of Event Report Export |
| 2 | NumberOfMandates | The number of distinct mandates | Int | 11 | Once per file | |
| 3 | NumberOfEvents | The number of events reported | Int | 11 | Once per file |