Supplier Payments Terms of Use

Morocco · Business

Effective September 17, 2026

This version applies to new commitments from its effective date. Notice rules and conditions applicable to existing customers are preserved; this publication is not a retroactive amendment of their contracts.

1. Scope

These conditions apply to an enabled Business payment to a supplier. They supplement the Broco Terms of Use — Morocco — Business and the agreement of the executing financial-service entity. Your accepted offer, mandate or confirmation states permitted countries, currencies, routes, fees, limits and provider roles.

Broco does not guarantee the supplier's performance or validate the commercial value of an invoice merely by processing its payment. Broco remains responsible for its own platform and instruction-handling obligations.

These conditions do not add a standalone Business FX service to the catalogue.

2. Instructions and supporting information

The Business must identify the supplier, destination account, amount, currency, invoice or purpose and authorised payer. It must have a lawful source of funding and authority to give the instruction. Necessary supporting records may be requested for eligibility and lawful checks.

Before confirmation, disclose the debit amount, expected destination amount or determination method, charges, conversion where relevant and expected execution. Apply any supported Business approvals configured for the instruction.

A supplier's changed payment details should be independently verified through a trusted channel. This precaution does not remove mandatory responsibility for a payment error or override the configured approval process.

3. Execution and cancellation

Receipt, irrevocability, rejection and return follow the actual payment agreement. A quote or uploaded invoice does not mean an instruction has been accepted or funds settled.

Request cancellation promptly. A recall after irrevocability may be attempted where supported, but recovery is not guaranteed. Disclose lawful recall costs before acceptance where required. A failed operation must be reconciled and any amount owed returned according to the relevant rules.

4. Availability and records

Keep confirmations, invoices and required business records. The interface must distinguish pending, completed and returned operations and identify justified adjustments.

5. Complaints

For an instruction error, suspected invoice fraud or execution problem, contact support@broco.app promptly. Complaints about the underlying goods or service remain directed to the supplier, without excluding a separate payment remedy.

6. Information that applies to your operation

Your accepted offer, mandate or transaction confirmation supplies the variable commercial details for the operation. Those details must be available before you commit; a general reference to this page does not replace information required at that point.

Only the functions expressly enabled for you are included. Published catalogue content does not establish availability. Changes to accepted terms remain subject to the applicable notice and other mandatory requirements; updating a screen is not, by itself, consent to a material change.

7. Business users and permissions

An organisation must appoint and manage the users allowed to act for it. It must ensure that users have appropriate authority and notify us when authority ends.

Payment approvals, access restrictions and account administration must follow the permissions configured for the relevant service. The organisation should review its users regularly and protect access when an employee or contractor leaves.

The operations available, approval rules, integrations, data responsibilities, treatment of instructions from authorised users and the process for correcting or revoking permissions are specified in your accepted Business agreement or service description.

Use of a business interface does not authorise the collection, disclosure or use of another person's data without an appropriate basis.

8. Fees and currency conversion

Applicable fees, pricing currency, taxes where relevant and transaction limits must be made available before you subscribe to a service or confirm an operation. Country-specific pricing may differ from a global marketing example.

Changes to fees must follow the notice and termination rules applicable to the service. Posting a new price on a webpage does not, on its own, replace a required contractual notice.

9. Complaints and disputed operations

You can contact support@broco.app with a complaint about Broco. Describe the service, relevant transaction reference and issue; do not send passwords or authentication codes.

Where another provider is responsible for a part of the service, your accepted offer, mandate or confirmation explains the complaint route and escalation available. This does not remove your ability to complain about Broco's own acts or omissions.

Complaints are handled within the deadlines required by applicable law and by any mandatory provider process. Any extension must be lawfully permitted and explained. Complaint handling does not replace a statutory remedy. Urgent procedures, required provider deadlines and external dispute-resolution bodies are identified in the applicable service information for your jurisdiction.

You do not have to complete an internal process where applicable law permits direct access to an authority or court. Contractual complaint procedures do not shorten mandatory limitation or notification periods.

10. Responsibility and remedies

Broco is responsible for performing its own contractual obligations. Where a service is provided by another entity, your accepted offer, mandate or confirmation identifies each party's responsibilities. Another entity's involvement does not remove responsibility that applicable law places on Broco, including for acts or omissions attributable to Broco.

Nothing in these conditions excludes or restricts liability or remedies that cannot lawfully be excluded or restricted. This includes mandatory rights applicable to unauthorised or incorrectly executed transactions where the relevant legal regime provides them.

A security incident, incorrect recipient information or breach of a user obligation will be assessed on the facts and under the applicable law. It is not an automatic basis to reject every claim.

Where a separate Business agreement includes a limitation of liability or indemnity, it must identify its scope and exceptions and preserve any rights that cannot be waived.

11. Morocco: Local service rules

Each activated financial or cash service must identify the actual provider and any mandated network within the scope of its permissions. Currency conversion and cross-border operations are available only through the permitted route stated in your accepted offer, mandate or confirmation. A pilot is not generally available merely because it appears in the catalogue. Agent and collection functions require the actual mandate, receipt and custody rules.