Legal documents
Terms and Conditions of Use
This is a translation provided for convenience. The French version is the only legally binding version and prevails in the event of any discrepancy.
These terms govern the opening and use of a BLEUGATSH account and every money transfer made to a beneficiary in the WAEMU through the BCEAO’s PI-SPI instant payment system. Please read them carefully: by creating an account, you accept them in full.
Preamble
The BLEUGATSH service is operated by BLEUGATSH TRADE OÜ, a private limited company incorporated under Estonian law [registration number, registered office address and share capital to be completed], hereinafter “BLEUGATSH”, “we” or “our”.
BLEUGATSH provides a digital service allowing an individual (the “Customer”) to send money to a relative or any other person (the “Beneficiary”) located in one of the eight countries of the West African Economic and Monetary Union (WAEMU). The Customer pays in euros or in stablecoins; the Beneficiary receives CFA francs (XOF) in the bank account or e-wallet linked to their PI-SPI alias.
These terms and conditions of use (the “Terms”), together with the fee schedule, the privacy policy, the anti-money laundering policy and the complaints procedure, form the entire agreement between the Customer and BLEUGATSH (the “Agreement”). In the event of a conflict, the Terms prevail, unless another document contains a provision more favourable to the Customer.
Article 1 — Definitions
In these Terms, the following terms, whether singular or plural, have the meaning given below:
- “PI-SPI Alias”: an identifier used to address a payment to a Beneficiary on PI-SPI without knowing their bank details (phone number, unique identifier or merchant code, possibly read from a QR code).
- “Application” or “Customer Area”: the web interface available at bleugatshpay.com, reserved for the authenticated Customer, from which they manage their account, Beneficiaries and Transfers.
- “Beneficiary”: the individual or legal entity designated by the Customer to receive the funds, identified by their PI-SPI Alias.
- “Account”: the Customer’s personal access to the service, protected by their email address, password and a second authentication factor. The Account is neither a payment account nor a deposit account: it cannot hold a balance.
- “Stablecoin”: a digital token whose value is pegged to the US dollar, accepted by BLEUGATSH as a means of payment (USDT and USDC) on the networks offered in the Application.
- “Quote”: the summary shown before each Transfer, stating the amount to pay, the fees, the exchange rate and the exact amount received in XOF.
- “Transfer”: the Customer’s order to transfer a set amount to a Beneficiary, from its creation to its final status.
- “Business Day”: a day from Monday to Friday, excluding public holidays in Estonia and closing days of the payment systems concerned.
- “Demo Mode”: a discovery mode of the Application, indicated on screen, in which no money is collected or paid out.
- “Live Mode”: the mode in which Transfers give rise to an actual payment by the Customer and an actual payout to the Beneficiary.
- “Payment Method”: the means of payment chosen by the Customer for a Transfer: bank card, Apple Pay, Google Pay, SEPA bank transfer or Stablecoin.
- “PI-SPI”: the Interoperable Platform of the instant payment system of the Central Bank of West African States (BCEAO), which enables instant XOF transfers between the accounts and wallets of WAEMU participants.
- “Provider”: any third-party institution or company used by BLEUGATSH to deliver the service, in particular for payment collection, identity verification, PI-SPI payout, hosting or messaging.
- “Final Status”: the status returned by PI-SPI confirming that the payment to the Beneficiary is irrevocable.
- “XOF”: the CFA franc of the African Financial Community, the common currency of the WAEMU States.
Article 2 — Purpose and scope
The purpose of the Terms is to set out the conditions under which BLEUGATSH makes the service available to the Customer, and the rights and obligations of each party.
The service is offered exclusively to individuals acting for personal, non-professional purposes. Transfers made as part of a commercial, non-profit or professional activity are not permitted without the prior written consent of BLEUGATSH.
The destination countries covered are: Benin, Burkina Faso, Côte d’Ivoire, Guinea-Bissau, Mali, Niger, Senegal and Togo. BLEUGATSH may suspend a destination country at any time for regulatory, technical or security reasons; the Customer is informed in the Application.
BLEUGATSH is not a bank. Amounts paid by the Customer are not deposits: they are allocated to the execution of the requested Transfer and do not earn interest. [Regulatory status of BLEUGATSH and, where applicable, the licensed institution on whose behalf the service is provided: to be specified before Live Mode opens.]
Article 3 — Acceptance and enforceability of the Terms
The Customer accepts the Terms by ticking the box provided for this purpose when creating their Account. This acceptance is recorded together with its date and the version of the Terms accepted.
The Terms can be accessed at any time from the website footer and from Settings → Our agreements in the Customer Area. The Customer may save or print them on a durable medium. They may also request a copy by email at any time, free of charge.
The version applicable to a Transfer is the one in force when that Transfer is created.
Article 4 — Eligibility
To open an Account, the Customer must meet all of the following conditions:
- be an individual aged at least 18 with full legal capacity;
- reside in a country from which BLEUGATSH offers the service [list of sending countries to be specified according to regulatory status];
- have a personal email address and a mobile phone number in their own name, or an authenticator app;
- not be subject to any sanction, asset freeze or prohibition imposed by the European Union, the United Nations, a Member State or a WAEMU State;
- act on their own behalf and not on behalf of a third party;
- not already hold a BLEUGATSH Account. Only one Account is allowed per person.
BLEUGATSH reserves the right to refuse to open an Account, without having to give reasons where the law prohibits it, in particular where the information provided is incomplete, inconsistent or cannot be verified.
Article 5 — Creating the Account, step by step
The Account is created entirely online, in the following order. No Transfer is possible until all steps are completed.
- Step 1 — Email address: the Customer enters their email address and accepts the Terms and the privacy policy.
- Step 2 — Email confirmation: a confirmation code or link is sent to that address. The Customer must validate it within the stated time; otherwise they can request a new one.
- Step 3 — Second authentication factor: the Customer chooses between an authenticator app (for example Google Authenticator) and receiving codes by SMS. They register this factor by entering a first valid code.
- Step 4 — Password: the Customer chooses a strong personal password that they do not use on any other service.
- Step 5 — Profile: the Customer enters their surname(s) and first name(s) as shown on their identity document, date of birth, country of residence, address and phone number.
- Step 6 — Identity verification: the Customer has their identity verified under the conditions of Article 6. This step is mandatory before any Transfer in Live Mode; Demo Mode remains available without it.
The Customer guarantees that the information provided is accurate, truthful and up to date. They undertake to update without delay in their Customer Area any information that has become inaccurate (address, phone, circumstances) and to provide supporting documents at BLEUGATSH’s request.
Article 6 — Identity verification and know your customer
In accordance with the regulations on combating money laundering and terrorist financing, BLEUGATSH must identify each Customer and verify their identity before executing any Transfer in Live Mode.
Verification is carried out online, with the help of a specialised Provider, and includes:
- a photograph of a valid official identity document (identity card, passport or residence permit);
- a selfie or short video confirming that the Customer is the holder of the document and is present;
- where applicable, proof of address dated within the last three months.
The result is shown in the Customer Area: “verified”, “under review”, “to be completed” or “rejected”. A rejected verification can be restarted where the reason allows it (blurred photo, expired document, etc.).
BLEUGATSH may at any time, in particular depending on the amount, frequency or nature of Transfers, request additional information or documents: occupation, source of funds, relationship with the Beneficiary, purpose of the Transfer, proof of income. Until these are provided, Transfers may be suspended.
The Customer undertakes to renew their verification when their identity document expires or when BLEUGATSH asks them to.
Article 7 — Account security and Customer obligations
The Customer is solely responsible for keeping their credentials (email address, password, second factor) safe and confidential. They undertake to:
- never share their password, SMS codes or authenticator app codes with anyone, including a person claiming to be a BLEUGATSH employee;
- use a personal device that is up to date and protected (lock code, current operating system);
- log out after each use on a shared device;
- check that they are on the bleugatshpay.com website before entering their credentials;
- report to BLEUGATSH without delay any loss, theft, misappropriation or unauthorised use of their Account or second factor.
BLEUGATSH will never ask you, by email, SMS, phone or messaging app, for your password, a login code or to make a “test” Transfer. Any such message must be treated as a fraud attempt and reported to us.
At each login, the Customer authenticates with their password and second factor. Some sensitive operations may require re-authentication. BLEUGATSH may end an inactive session or all open sessions if there is any doubt about the Account’s security.
Upon a report, BLEUGATSH blocks access to the Account and any pending Transfers as soon as possible, then helps the Customer restore secure access.
Article 8 — Beneficiaries
The Customer registers Beneficiaries in their Customer Area by entering their full name, country and PI-SPI Alias. They may give them a nickname.
Before the first Transfer, BLEUGATSH checks that the PI-SPI Alias exists and is active. Where PI-SPI allows it, the name of the alias holder is shown to the Customer, who must make sure it matches the person they intend to pay.
The Customer is solely responsible for the accuracy of the PI-SPI Alias entered. A Transfer executed to the alias given by the Customer is deemed correctly executed, even if that alias does not belong to the person the Customer thought they were paying (see Article 21).
The Customer may edit or delete a Beneficiary at any time. Deletion has no effect on Transfers already created.
Scam warning: never send money to someone you do not know personally, or in response to a job, investment, loan, prize or dating offer, or an urgent request received online. A Transfer credited to the Beneficiary is irrevocable and generally cannot be recovered.
Article 9 — Demo Mode
Demo Mode lets the Customer explore the entire journey (Quote, payment, tracking, receipt) without any movement of money. It is always indicated by the “Demo / Live” selector in the Application.
In Demo Mode, no payment is collected, no real deposit address or bank details are provided, and no payout is made to the Beneficiary. The rates and fees displayed are those of the service, for information. Receipts and notifications produced are marked “Demo” and have no value as proof of payment.
The Customer must never send funds to an address or details displayed in Demo Mode. Demo Mode and Live Mode Transfers are strictly separated.
Article 10 — How a Transfer works
Each Transfer follows the steps below. The Customer can track its progress at any time from their activity and receives a notification at each important step.
- Step 1 — Choice of Payment Method: bank card, Apple Pay or Google Pay, bank transfer, or Stablecoin.
- Step 2 — Amount: the Customer enters the amount they wish to pay. The amount received in XOF is calculated and displayed immediately.
- Step 3 — Beneficiary: the Customer chooses a verified Beneficiary or adds a new one.
- Step 4 — Summary and Quote: the Customer checks the amount paid, the fees, the rate applied, the exact amount received by the Beneficiary, and the Beneficiary’s name and alias. They confirm the Transfer. This confirmation constitutes a payment order and consent to the Transfer.
- Step 5 — Payment: the Customer pays the amount according to the rules specific to the chosen Payment Method (Articles 12 to 14), within the stated time.
- Step 6 — Receipt and checking of funds: BLEUGATSH checks that the payment has been received, for the right amount and in the right currency, and carries out its compliance checks (Article 15).
- Step 7 — PI-SPI payout: BLEUGATSH initiates the instant payment of the agreed XOF amount to the Beneficiary’s PI-SPI Alias (Article 16).
- Step 8 — Confirmation: when PI-SPI returns the Final Status, the Transfer moves to “Credited”. The receipt is available in the Application and emailed to the Customer.
A Transfer can only be confirmed once. The same request sent several times (double click, page reload, lost connection) never creates several Transfers or several payments.
Article 11 — Quote, exchange rate and fees
The Quote is calculated by BLEUGATSH’s servers when the Transfer is created; no amount calculated by the Customer’s browser is taken into account.
Exchange rate: for payments in euros (card, Apple Pay, Google Pay, bank transfer), the rate applied is the fixed parity €1 = 655.957 XOF. For Stablecoin payments, the rate applied is the market rate obtained by BLEUGATSH at the time of the Quote; it is shown to the Customer and locked for the Transfer.
Fees: BLEUGATSH’s fees are expressed as a percentage of the amount paid, depending on the Payment Method, and appear in the fee schedule published on the website. They are deducted from the amount paid before conversion. Example: for €100 paid by card with 4% fees, the fees are €4 and the Beneficiary receives 96 × 655.957 = 62,971 XOF (rounded down).
Rounding: the amount received in XOF is rounded down to the nearest franc. Fees are rounded to the nearest euro cent (or to the sixth decimal place for Stablecoins).
The amount received shown in the Quote is what the Beneficiary receives. BLEUGATSH charges no additional fee to the Beneficiary. However, the following remain payable by the Customer and outside BLEUGATSH’s control: any fees charged by their own bank for a transfer or card transaction (particularly outside the euro area), blockchain network fees for a Stablecoin payment, and, where applicable, withdrawal or account fees charged to the Beneficiary by their own institution.
Validity: the Quote is valid for the payment period specific to the chosen Payment Method, shown in the Application. After this period, the Transfer expires (Article 18) and a new Quote must be issued.
BLEUGATSH may change its fee schedule. New fees only apply to Transfers created after their publication and, for existing Customers, under the conditions of Article 34.
Article 12 — Payment by bank card, Apple Pay or Google Pay
Payment is made in a secure form provided by the collection Provider and embedded in the Application. BLEUGATSH never has access to the full card number or security code and does not store them.
The card or wallet used must be in the Customer’s name. Anonymous prepaid cards are not accepted. Payment is subject to strong authentication by the card issuer (3-D Secure): the Customer must approve it in their banking app or by the method offered by their bank.
The payment period is 30 minutes from the creation of the Transfer. If the card is declined, the Customer may try again with the same or another method until the period expires, with no risk of being charged twice for the same Transfer.
The amount is debited in euros, in a single payment, upon authorisation. If several payments were approved for the same Transfer, BLEUGATSH detects this automatically, places the Transfer under review and refunds the excess payment.
The Customer must not dispute with their bank a payment corresponding to a Transfer they authorised and that has been credited. An abusive chargeback may lead to suspension of the Account and recovery of the amounts concerned.
Article 13 — Payment by bank transfer
After the Transfer is confirmed, the Application displays BLEUGATSH’s bank details (account holder, IBAN, BIC) and a unique reference in the format BG-XXXXXXXX, specific to that Transfer.
For the bank transfer to be matched automatically to the Transfer, the Customer must follow these four rules:
- the bank transfer must be sent from a bank account in the name of the Customer, the holder of the BLEUGATSH Account;
- the BG-XXXXXXXX reference must appear in the transfer description or reference field;
- the amount transferred must be exactly the amount indicated, in euros;
- the bank transfer must be sent within three days of the creation of the Transfer.
BLEUGATSH recommends using SEPA Instant Credit Transfer when the Customer’s bank offers it. A standard SEPA transfer is usually received within one Business Day.
If one of the rules is not followed (missing reference, different amount, different payer name, transfer received after expiry), the bank transfer is not automatically rejected: the Transfer is placed “Under review” and examined by the BLEUGATSH team. Depending on the case, the Transfer continues after the Customer’s confirmation, or the funds are returned to the originating account, less any bank return fees.
A bank transfer received without an identifiable reference that cannot be linked to a Customer is returned to the sender.
Article 14 — Payment in Stablecoins
The Customer chooses the Stablecoin (USDT or USDC) and the blockchain network from those offered. The Application then shows a deposit address dedicated to that Transfer, the exact amount to send, the network to use and, where applicable, a memo or tag. A QR code contains this information.
The Customer undertakes to:
- send exactly the Stablecoin and amount indicated, on the network indicated, from a wallet they personally control;
- never reuse a deposit address for another Transfer;
- make the deposit within the time shown (60 minutes at most, unless otherwise stated).
Warning: a deposit sent on a network other than the one indicated, or of a different asset, may be permanently lost. BLEUGATSH will make reasonable efforts, without any guarantee of success, to recover such funds where technically possible; the costs incurred will then be deducted.
The Transfer moves to “Funds received” once the deposit has received the number of confirmations required by the network. A deposit that has been detected but not yet confirmed never causes the Transfer to expire.
Special cases, examined by the team: a deposit lower than the expected amount, a deposit received after expiry or an inconsistent deposit places the Transfer “Under review”. The Customer is contacted to complete the payment or to have the funds returned. A deposit higher than the expected amount is flagged; the excess is returned at the Customer’s request, less network fees.
Any return of Stablecoins is made to an address belonging to the Customer, on the same network, less network fees. It may require additional identity checks.
Article 15 — Receipt of funds and checks
A notification received from a Provider is never, on its own, proof of payment. BLEUGATSH always re-checks the payment with the Provider concerned before treating the funds as received.
Before any payout, BLEUGATSH checks in particular that the amount, currency and payer identity match, that neither the Customer nor the Beneficiary appears on a sanctions list, that the limits are respected and that the Transfer is consistent with the Customer’s profile.
Where these checks require human review, the Transfer is placed “Under review”. The Customer is informed. Review normally takes less than two Business Days, unless additional documents are requested.
Article 16 — Payout to the Beneficiary via PI-SPI
As soon as the funds have been received and checked, BLEUGATSH initiates the payout of the agreed XOF amount to the Beneficiary’s PI-SPI Alias. The payout is normally made within seconds and no later than the end of the Business Day following receipt of the funds, unless a check is in progress or PI-SPI or the Beneficiary’s institution is unavailable.
Each Transfer receives a unique, stable transaction identifier. In the event of a technical incident during the payout, BLEUGATSH always checks with PI-SPI whether the payment has been made before any new attempt: the same Transfer can never be paid out twice.
The Transfer is “Credited” when PI-SPI returns the Final Status. From that moment, the payment is irrevocable: neither the Customer nor BLEUGATSH can cancel it. The funds are then available to the Beneficiary at their institution, subject to that institution’s terms.
If PI-SPI or the Beneficiary’s institution rejects the payout (closed alias, blocked account, Beneficiary limit reached, etc.), the Transfer moves to “Payout failed” and Article 19 applies.
Article 17 — Transfer statuses
At any time, a Transfer is in one of the following statuses, shown in the Application:
- “Awaiting payment”: the Transfer has been created and BLEUGATSH is waiting for the Customer’s payment;
- “Funds received”: the payment has been received and checked;
- “Payout in progress”: the PI-SPI payout has been initiated and is awaiting the Final Status;
- “Credited”: the Beneficiary has received the funds (final status);
- “Under review”: the Transfer is being examined by the BLEUGATSH team;
- “Payout failed”: the payout has been rejected;
- “Refund in progress” then “Refunded”: the funds are returned to the Customer (final status);
- “Cancelled”: the Transfer was cancelled before any payment (final status);
- “Expired”: the payment was not received within the time allowed (final status, except for late payment).
Article 18 — Cancellation and expiry
Cancellation: the Customer may cancel a Transfer from the Application while it is “Awaiting payment” and no payment has been initiated. Once a card payment has been started or a Stablecoin deposit detected, cancellation is no longer possible from the Application: the Customer must contact support.
A “Credited” Transfer can never be cancelled.
Expiry: a Transfer whose payment is not received within the period specific to the Payment Method (30 minutes for cards and wallets, 60 minutes for Stablecoins, 3 days for bank transfers) expires automatically. No fee is due for an expired or cancelled Transfer.
Late payment: if a payment is nevertheless received after expiry, the Transfer moves to “Under review”. BLEUGATSH contacts the Customer, who chooses between continuing the Transfer (based on a new Quote if the rate has changed) and having the funds returned.
Article 19 — Failed payout and refund
If the payout fails, BLEUGATSH informs the Customer and offers, as appropriate, to correct the Beneficiary’s PI-SPI Alias or to be refunded.
Refund methods by Payment Method:
- card, Apple Pay, Google Pay: automatic refund to the card used. The time it takes to appear on the statement depends on the Customer’s bank (generally 3 to 10 Business Days);
- bank transfer: return to the originating bank account, in the Customer’s name;
- Stablecoins: return to an address belonging to the Customer, on the same network, less network fees.
Where the failure is not attributable to the Customer, the refund covers the full amount paid, including BLEUGATSH’s fees. Where the failure results from an error or inaccurate information provided by the Customer, BLEUGATSH may keep its fees and deduct the external costs actually incurred, details of which are provided to the Customer.
BLEUGATSH makes the refund no later than ten Business Days after the failure is established, unless legally required to retain the funds (in particular at the request of an authority).
Article 20 — Transfers under review
A Transfer may be placed “Under review” for any of the following reasons: different amount or payer name, late or partial payment, double payment, request for documents, compliance check, security alert.
During the review, no payout is made. The Customer may be contacted by email or through support in the Application. They undertake to respond as soon as possible and to provide the information requested.
At the end of the review, the Transfer is either continued, refunded in accordance with Article 19, or blocked where required by law. In the latter case, BLEUGATSH may be legally prohibited from informing the Customer of the reasons.
Article 21 — Errors, unauthorised transactions and disputes
Customer alias error: where the Customer entered an incorrect PI-SPI Alias and the Transfer has been credited, BLEUGATSH is not required to refund the Customer. At the Customer’s request, BLEUGATSH will take reasonable steps, without guarantee of success, to try to recover the funds from the Beneficiary’s institution and will provide the Customer with the information it holds so that they can exercise their rights.
BLEUGATSH error: where a Transfer has not been executed, has been executed incorrectly or for an amount different from the Quote due to BLEUGATSH, BLEUGATSH will promptly put things right (payment of the difference or full refund, fees included).
Unauthorised transaction: a Customer who notices a Transfer they did not authorise must report it to BLEUGATSH without delay, and at the latest within 13 months of the debit date [period to be confirmed according to regulatory status]. After verification, and except in the case of fraud or gross negligence by the Customer (in particular sharing their credentials or codes with a third party), BLEUGATSH refunds the unauthorised Transfer.
Any dispute follows the complaints procedure described in Article 35.
Article 22 — Limits
For the security of Customers and to comply with anti-money laundering obligations, the following limits apply in Live Mode:
- a maximum of 2,000,000 XOF received per Transfer;
- a maximum of 3,000,000 XOF received over a rolling 24 hours, all Transfers combined;
- a maximum of 10 Transfers over a rolling 24 hours;
- a maximum of 3 Transfers “Awaiting payment” at the same time.
The Customer can check their available limit at any time in the Application (Settings → Fees and limits). Cancelled, expired or refunded Transfers are not counted.
BLEUGATSH may lower these limits for a Customer where their situation justifies it, or raise them at the Customer’s request after additional verification. Any general change to the limits is published in the Application and in the fee schedule.
Article 23 — Refusal, suspension and blocking
BLEUGATSH may refuse to execute a Transfer, suspend it or suspend access to the Account, in particular in the following cases:
- inaccurate, incomplete or unverifiable information;
- failure to respond to a request for documents;
- suspicion of fraud, of a scam of which the Customer may be a victim, of identity theft or of unauthorised use of the Account;
- suspicion of money laundering, terrorist financing or breach of a sanctions measure;
- breach of these Terms or prohibited use within the meaning of Article 24;
- request from a judicial or administrative authority;
- risk to the security of the service or other Customers.
Unless prohibited by law, BLEUGATSH informs the Customer of the refusal or suspension, the reasons for it and, where applicable, the steps to take to remedy it.
Article 24 — Prohibited uses
It is strictly prohibited to use the service:
- for funds of illicit origin or to finance an illegal activity;
- on behalf of a third party, or by lending one’s Account to another person;
- to pay for illicit goods or services, unauthorised gambling, weapons, narcotics or any illegal content;
- to circumvent an international sanctions measure or the service limits (for example by deliberately splitting a Transfer);
- for a professional or commercial activity without BLEUGATSH’s consent;
- by creating several Accounts, using a false identity or another person’s documents;
- by attempting to gain unauthorised access to BLEUGATSH’s systems, disrupt their operation or extract their data by automated means.
Any breach may result in immediate termination of the Account, reporting to the competent authorities and liability of the Customer.
Article 25 — Communications and notifications
Communications between the Customer and BLEUGATSH take place in French. Translations of the website and of these documents are provided for convenience only.
BLEUGATSH communicates with the Customer by email to the address associated with the Account, by notifications in the Application and, where applicable, by SMS. The Customer receives in particular a notification at each important step of their Transfers (payment received, credited, under review, failure, refund, expiry).
The Customer undertakes to keep a valid email address and to check their messages and notification centre regularly. Information relating to a Transfer is deemed received as soon as it is made available in the Application.
The Customer can contact BLEUGATSH at any time from the Support section of the Application, or by email at blanchard@bleugatshpay.com.
Article 26 — Receipts, history and evidence
For each credited Transfer, a PDF receipt is made available in the Application and attached to the confirmation email. It states in particular the date, the amount paid, the fees, the rate, the amount received in XOF, the Beneficiary, their alias and the PI-SPI reference of the transaction.
The Customer can view the complete history of their Transfers and download a statement at any time from their activity.
The computer records of BLEUGATSH and its Providers (timestamps, login logs, confirmations from Providers and PI-SPI) are authoritative between the parties, unless the Customer proves otherwise.
BLEUGATSH retains data relating to Transfers for the period required by regulations (in principle five years from the end of the business relationship), under the conditions set out in the privacy policy.
Article 27 — Service availability
BLEUGATSH strives to make the service available 24 hours a day, 7 days a week. The service may however be interrupted, in particular for maintenance, updates, technical incidents, or unavailability of a Provider, PI-SPI or telecommunications networks.
Planned interventions are, as far as possible, announced in advance in the Application. During an interruption, Transfers in progress are preserved and resume processing as soon as the service is restored; no Transfer is paid out twice because of an interruption.
Article 28 — Liability of BLEUGATSH
BLEUGATSH undertakes to execute Transfers diligently, in accordance with the Quote accepted by the Customer and these Terms.
BLEUGATSH is not liable for:
- the consequences of inaccurate information provided by the Customer, in particular a PI-SPI Alias error;
- the use made of the funds by the Beneficiary, or the relationship between the Customer and the Beneficiary;
- delays or refusals attributable to the Beneficiary’s institution, the Customer’s bank, blockchain networks or PI-SPI, subject to its own monitoring obligations;
- indirect damage such as loss of opportunity, operating loss or non-material damage, to the extent permitted by law;
- the consequences of a force majeure event.
Nothing in these Terms limits BLEUGATSH’s liability for gross negligence or wilful misconduct, or the rights the Customer enjoys as a consumer under mandatory legal provisions.
Article 29 — Liability of the Customer
The Customer is responsible for the use of their Account, the accuracy of the information they provide, the choice of their Beneficiaries and compliance with these Terms.
The Customer indemnifies BLEUGATSH against any consequence of fraudulent or prohibited use of the service on their part, and reimburses any amounts BLEUGATSH has had to bear because of their breach (in particular in the event of an abusive card chargeback).
Article 30 — Force majeure
Neither party is liable for failure to perform its obligations where this results from a force majeure event within the meaning of the applicable law: natural disaster, armed conflict, riot, general network failure, large-scale cyberattack, decision of an authority, prolonged unavailability of PI-SPI, etc.
The affected party informs the other as soon as possible. Transfers awaiting payment may be cancelled free of charge; funds already received are paid out as soon as the event ends, or refunded if the impediment lasts more than thirty days.
Article 31 — Referral programme
The Customer may invite friends and family to join BLEUGATSH using their personal referral code.
The referrer receives a €5 credit when the referred person, having entered the code before their first transaction, makes a first Live Mode Transfer of at least €50 excluding fees that is actually credited. Demo Mode, cancelled, expired or refunded Transfers are not taken into account.
A person can only have one referrer. The Customer cannot use their own code or refer a person who already has an Account.
Validated credits can be requested for payout via PI-SPI to one of the Customer’s Beneficiaries, after identity verification. A credit reserved by a pending request cannot be requested a second time; cancelling an unprocessed request releases it.
Any abuse (fake accounts, self-referral, misleading solicitation, publishing the code on deal or cashback sites without authorisation) results in the cancellation of the credits concerned and may lead to suspension of the Account. BLEUGATSH may change or end the programme at any time for the future; credits already validated remain acquired.
Article 32 — Intellectual property
The BLEUGATSH brand, logos, Application, website, and their content, text, graphics and software are the exclusive property of BLEUGATSH or its partners and are protected by intellectual property law.
The Customer is granted a personal, non-exclusive, non-transferable right to use the Application, solely for the duration of the Agreement and for the purposes of the service. Any full or partial reproduction, extraction or reuse without written authorisation is prohibited.
Third-party trademarks and logos (PI-SPI, card networks, wallets, crypto-assets) belong to their respective owners and are mentioned for information.
Article 33 — Personal data
BLEUGATSH processes the personal data of the Customer and their Beneficiaries to provide the service, meet its legal obligations and ensure the security of transactions, in compliance with the General Data Protection Regulation (GDPR).
Details of the data processed, purposes, recipients, transfers outside the European Union (in particular to WAEMU countries to execute the payout), retention periods and the Customer’s rights are set out in the privacy policy, which forms an integral part of the Agreement.
By registering a Beneficiary, the Customer undertakes to inform them that their data (name, country, alias) is shared with BLEUGATSH for the purposes of the Transfer.
Article 34 — Term, right of withdrawal and termination
Term: the Agreement is concluded for an indefinite period from the creation of the Account.
Right of withdrawal: the Customer has 14 calendar days from acceptance of the Terms to withdraw, free of charge and without giving any reason, by writing to support or to blanchard@bleugatshpay.com. By requesting the execution of a Transfer during this period, the Customer expressly agrees that the Transfer is executed immediately; an executed Transfer can no longer be withdrawn.
Termination by the Customer: the Customer may terminate the Agreement and close their Account at any time, free of charge, via support in the Application or by email. Closure takes effect once all Transfers in progress have been fully processed.
Termination by BLEUGATSH: BLEUGATSH may terminate the Agreement with two months’ notice sent by email. It may terminate without notice in the event of a serious breach by the Customer (fraud, prohibited use, false statements, persistent refusal to provide requested documents) or where required by law.
Effects: when the Account is closed, Transfers awaiting payment are cancelled, Transfers whose funds have been received are completed or refunded, and validated referral credits are paid out on request within three months. Data is retained for the legal periods, then deleted.
Inactive Account: an Account with no login for 24 months may be closed by BLEUGATSH after informing the Customer by email, with two months’ notice.
Article 35 — Complaints and mediation
Any complaint can be sent to BLEUGATSH from the Support section of the Application (preferably from the Transfer concerned, via “Help with this transfer”) or by email to blanchard@bleugatshpay.com.
BLEUGATSH acknowledges receipt of the complaint within two Business Days and responds within fifteen Business Days. In exceptional circumstances, this period may be extended to thirty-five Business Days; the Customer is then informed of the reasons for the delay.
If the response does not satisfy them, or in the absence of a response within these periods, a consumer Customer may refer the matter free of charge to the competent mediator: [name and contact details of the mediator to be specified]. They may also use the European online dispute resolution platform, where available, or contact the competent supervisory authority: [to be specified according to regulatory status].
The detailed procedure is set out on the “Complaints” page of the website.
Article 36 — Changes to the Terms
BLEUGATSH may amend these Terms, in particular to take account of legal, regulatory, technical or service changes.
Any change is notified to the Customer by email and in the Application at least two months before it takes effect. A Customer who does not accept the change may terminate the Agreement free of charge before that date. Failing termination, they are deemed to have accepted the change.
Changes required by law, or that are exclusively favourable to the Customer (lower fees, new free feature), may apply immediately.
Article 37 — Governing law and jurisdiction
The Agreement is governed by [the applicable law to be specified according to regulatory status and country of establishment].
In accordance with the rules applicable to consumer contracts, this choice does not deprive the Customer of the protection afforded by the mandatory provisions of the law of the country in which they are habitually resident.
Failing an amicable settlement or mediation, any dispute falls within the jurisdiction of the competent courts under ordinary rules; a consumer Customer may always bring proceedings before the court of their place of residence.
Article 38 — Miscellaneous
If any provision of the Terms is declared void or unenforceable, the other provisions remain in full force and effect.
BLEUGATSH’s failure to rely on a breach by the Customer does not constitute a waiver of its right to rely on it later.
The Customer may not assign or transfer their rights and obligations under the Agreement without BLEUGATSH’s written consent. BLEUGATSH may assign the Agreement to any entity taking over all or part of its business, after informing the Customer, who then retains the right to terminate free of charge.
The Terms are drafted in French. This English version is a translation; in the event of any discrepancy, the French version prevails.
Article 39 — Contact us
BLEUGATSH TRADE OÜ — [registered office address to be completed]. Support: Support section of the Customer Area. Email: blanchard@bleugatshpay.com. Website: bleugatshpay.com.
Version of 16 November 2026 — document under legal review.
BLEUGATSH