Prompt
Prompt di IA legale per FinTech / Payments
14 prompts you can paste straight into HAQQ or any other assistant. Every one is written out in full. Open it, copy it, change the bracketed parts.
Registering an Investment Fund With the CMAChecklistEnterpriseCompliance / Due Diligence
Act as CMA counsel. A [foreign / locally licensed] entity wants to register a [public / private / simplified] investment fund in Saudi Arabia to invest in [describe the strategy and asset class]. Set out the conditions: 1. Whether the sponsor itself needs a CMA licence to act as fund manager, and which activity that licence covers. This determines whether the whole plan is possible before anything else matters. 2. Every condition for registering a fund of this specific type: minimum capital, permitted investors, custodian and administrator requirements, board or committee composition, and the auditor. 3. What must be in the terms and conditions document, and the disclosures the CMA will require for this asset class. 4. The filing route: forms, language, fees, the review timeline, and what typically triggers a second round of comments. 5. Ongoing obligations after registration: reporting, valuation frequency, disclosure, and the events requiring prior CMA approval. 6. Where a foreign sponsor is treated differently from a local one, in a two-column table. Mandatory rules: cite the CMA rules, the Investment Funds Regulations and the Capital Market Law by name and article. These rules change; where you cannot confirm the current version, mark the item for verification against the CMA's own published rulebook rather than stating it as current.
Payment Services AgreementAgreementExpertDraft / Generate
You are drafting a payment services agreement for [Payment Provider] to process payments for [Merchant]. Facts: payment provider [Payment Provider], merchant [Merchant], the payment methods and settlement currency as described by the client. Deliverables: 1. Transaction fee structure, including how fees are calculated and when they are charged. 2. Settlement terms: timing, currency conversion if applicable, and conditions for delay or suspension. 3. Chargeback handling: process, timelines, and allocation of chargeback losses between the parties. 4. Reserve requirements: how the reserve is calculated, held, and released. 5. Data security standards, including PCI DSS compliance obligations for each party. 6. Regulatory compliance obligations relevant to payment processing in the merchant's operating jurisdiction. 7. Liability allocation, including caps and carve outs for fraud or non compliance. Mandatory rules: do not state that a specific payment services license or registration is not required without the merchant's jurisdiction being given; where it is not given, flag the licensing question for confirmation rather than assuming none applies. Cite the specific PCI DSS requirement or payment regulation relied on for each compliance obligation stated, and flag as unconfirmed any obligation you cannot tie to a named rule or standard.
E-Money License Application MemoMemoEnterpriseCompliance / Due Diligence
You are advising [Company] on obtaining an e-money license in [jurisdiction]. Facts: [Company]'s proposed business model, the e-money products it intends to issue, and its current corporate structure and ownership. Prepare a memo covering: 1. The licensing regime and the regulator responsible for e-money licenses in [jurisdiction]. 2. Capital requirements, both initial and ongoing, and how they are calculated. 3. Governance requirements, including fit-and-proper standards for directors and controllers. 4. AML/KYC obligations that attach to an e-money license specifically. 5. Safeguarding requirements for customer funds, including permitted safeguarding methods. 6. The application process and documentation required. 7. A realistic timeline from application to license grant, and the main risks of delay. Mandatory rules: cite the specific statute, regulation, or regulator guidance in [jurisdiction] behind each requirement rather than describing e-money licensing generically. Flag any capital figure, timeline, or requirement you cannot attribute to a named source, and mark it for confirmation with [jurisdiction] regulatory counsel before it is relied on. This memo is a drafting and analysis aid for a qualified practitioner, not a substitute for a formal regulatory opinion.
Open Banking API TermsAgreementExpertDraft / Generate
You are drafting API terms of service for [Bank/FinTech], covering the open banking APIs it makes available to third-party providers. Facts: the API scope (account information, payment initiation, or both), the third-party onboarding and authentication method, and the applicable regime, [PSD2/open banking regulation]. Deliverables, as sections of one set of terms: 1. Access and credentials: registration, API key issuance, sandbox versus production access, and grounds for suspension or revocation. 2. Rate limits and service levels: call volume caps, throttling, uptime commitment, and support response times. 3. Data usage restrictions: what customer data a third-party provider may access, retention limits, and prohibited secondary uses. 4. Security requirements: authentication standard, encryption in transit and at rest, and incident notification timelines. 5. Liability and indemnity: how loss from unauthorized access, data misuse, or service failure is allocated between [Bank/FinTech] and the third-party provider. 6. Regulatory compliance obligations tied to [PSD2/open banking regulation], including strong customer authentication and consent management. 7. Term, suspension, and termination, including the effect of a third-party provider losing its regulatory authorization. Mandatory rules: do not state a specific rate limit, liability cap, or compliance deadline as settled unless it is drawn from [Bank/FinTech]'s own policy or the named regulation, otherwise mark it as open for the client to confirm. This is a drafting aid for a qualified lawyer to review, not a substitute for regulatory advice.
Cryptocurrency Exchange TermsAgreementExpertDraft / Generate
You are drafting for [Crypto Exchange], to operate under the law of [jurisdiction]. Facts: the products offered (spot trading, custody, other), the categories of user permitted, and the license or registration [Crypto Exchange] holds or is seeking in [jurisdiction]. Draft terms of service covering: 1. Account registration and eligibility, including any restricted jurisdictions or user categories. 2. KYC and identity verification requirements. 3. Trading rules, including order types, market conduct restrictions, and suspension rights. 4. Custody of assets, stating whether client assets are segregated and how they are held. 5. Security measures and the allocation of loss in the event of a breach. 6. Withdrawal limits and processing times. 7. Fee structure. 8. Risk disclosures specific to digital assets, including volatility and the risk of total loss. Mandatory rules: cite the specific [jurisdiction] license, registration, or regulatory framework under which [Crypto Exchange] operates rather than asserting regulatory compliance in general terms. Flag any custody or disclosure requirement under [jurisdiction] law you cannot confirm. This document is a drafting aid for a qualified practitioner and does not replace regulatory legal advice before publication.
BNPL Platform AgreementAgreementExpertDraft / Generate
You are drafting a buy now pay later platform agreement between [BNPL Provider] and [Merchant]. Facts: the products or services sold, the instalment structure offered to customers, the integration method (API, plugin, or hosted checkout), and the merchant's sector. Deliverables, as sections of one agreement: 1. Integration requirements: technical specifications, testing and go live process, and ongoing maintenance obligations. 2. Payment terms: settlement timing, reserve or holdback amounts, and currency. 3. Merchant fees: transaction fees, chargeback fees, and any minimum volume commitments. 4. Customer credit assessment: who runs the affordability check, what data the merchant must pass through, and how a declined application is handled. 5. Default handling: consequences of a customer missing an instalment, and any recourse against the merchant. 6. Returns and refunds: how a return unwinds an instalment plan and who bears the cost of the reversal. 7. Consumer credit regulation compliance: disclosure obligations, cooling off rights, and marketing restrictions that apply to the instalment product. Mandatory rules: do not assert that a specific consumer credit rule or disclosure requirement applies without naming the source provision, flag it for confirmation instead. Note that the output is a drafting aid for a qualified lawyer to review before use, not legal advice to either party.
Digital Wallet TermsAgreementAdvancedDraft / Generate
You are drafting terms of service for [Company's] digital wallet application. Facts: the wallet's funding sources, the currencies or assets it holds, and the jurisdictions it will operate in. Deliverables, as sections of one set of terms: 1. Account setup: eligibility, identity verification, and account limits. 2. Funding methods: linked bank accounts, cards, and any minimum or maximum load amounts. 3. Transaction limits: daily, monthly, and per transaction caps, and how they can be raised. 4. Security features: authentication requirements, device binding, and fraud monitoring. 5. Unauthorized transaction liability: how loss is allocated between [Company's] business and the user, and the notification window that triggers protection. 6. Data privacy: what user data is collected, how it is used, and retention periods. 7. Dispute resolution procedures: how a user raises a transaction dispute and the timeline for resolving it. Mandatory rules: do not state a specific liability cap or notification window as settled unless it is drawn from [Company's] own policy, mark it for confirmation instead. Include a line that this is a drafting aid for a qualified lawyer to review, not legal advice.
AML/KYC PolicyPolicyExpertDraft / Generate
You are drafting for [FinTech Company], operating under the AML/CFT regime of [jurisdiction]. Facts: the products and customer types [FinTech Company] serves, and the regulator it reports to in [jurisdiction]. Draft an AML/KYC policy covering: 1. Customer identification and verification procedures, by customer risk category. 2. Risk assessment methodology, including the factors that raise a customer to enhanced due diligence. 3. Ongoing monitoring of transactions and triggers for review. 4. Suspicious activity reporting: internal escalation, and the filing obligation to the [jurisdiction] regulator or financial intelligence unit. 5. Record keeping requirements, including retention periods. 6. Staff training requirements and frequency. 7. Regulatory filing obligations and reporting deadlines. Mandatory rules: cite the specific [jurisdiction] statute, regulation, or regulator guidance behind each obligation rather than describing AML practice generically. Flag any retention period, reporting deadline, or threshold you cannot attribute to a named provision, and mark it for confirmation by the company's compliance counsel before adoption.
Lending Platform TermsAgreementExpertDraft / Generate
You are drafting for [Lending Platform], offering [consumer/SME] loans under the law of [jurisdiction]. Facts: the loan product terms (amount range, tenor, interest structure), and the license [Lending Platform] holds or is seeking to lend in [jurisdiction]. Draft terms of service covering: 1. Loan application process and eligibility criteria. 2. Credit assessment methodology and what happens if an application is declined. 3. Interest rate disclosure, including the annual percentage rate or its [jurisdiction] equivalent. 4. Repayment terms, including schedule, early repayment, and any fee for it. 5. Default consequences, including any acceleration clause. 6. Collection practices, consistent with [jurisdiction] debt collection rules. 7. Consumer protection compliance specific to [consumer/SME] lending in [jurisdiction]. Mandatory rules: cite the specific consumer protection statute or lending regulation of [jurisdiction] behind each disclosure requirement rather than stating a disclosure standard as universal. Flag any interest rate cap, cooling-off period, or disclosure format you cannot confirm under [jurisdiction] law rather than drafting around an assumed figure.
Payment Facilitator AgreementAgreementEnterpriseDraft / Generate
You are drafting a payment facilitator agreement between [PayFac] and [Acquiring Bank]. Facts: the card networks and payment methods [PayFac] will support, the sub-merchant categories it intends to onboard, and the settlement currency. Deliverables, as sections of one agreement: 1. Sub-merchant underwriting: the diligence [PayFac] must run before onboarding a sub-merchant, and the categories requiring [Acquiring Bank]'s prior approval. 2. Transaction monitoring: the fraud and anti-money-laundering monitoring obligations, and reporting cadence to [Acquiring Bank]. 3. Chargeback management: responsibility for handling disputes, chargeback thresholds, and consequences of exceeding them. 4. Reserve requirements: how a reserve is calculated, held, and released, and the circumstances that let [Acquiring Bank] increase it. 5. Regulatory compliance: card network rules, sanctions screening, and licensing obligations each party carries. 6. Liability allocation: how loss from a sub-merchant default, fraud, or a data breach is split between [PayFac] and [Acquiring Bank]. 7. Term, suspension, and termination, including the wind down of sub-merchant accounts if the agreement ends. Mandatory rules: do not state a specific reserve percentage, chargeback threshold, or regulatory obligation as settled unless it is drawn from a named card network rule, regulation, or the parties' own policy, otherwise mark it for confirmation. This is a drafting aid for a qualified lawyer to review, not a substitute for regulatory advice.
Cross-Border Payment Compliance ReviewReportExpertCompliance / Due Diligence
You are conducting a compliance review of [Company's] cross-border payment operations. Facts: the payment corridors [Company's] business operates in, the currencies handled, and the specific [jurisdictions] in scope for this review. Deliverables: 1. A summary of licensing requirements for payment or money transmission activity in each of the [jurisdictions], and whether [Company's] business currently holds the relevant authorization. 2. A review of sanctions screening controls, including list coverage and the point in the transaction flow where screening occurs. 3. An assessment of applicable FX regulations, including reporting thresholds and any restrictions on the currencies involved. 4. A review of correspondent banking relationships, including any concentration risk if a single correspondent bank were to exit. 5. A list of regulatory reporting obligations that apply in each of the [jurisdictions], with filing frequency and the authority each report goes to. 6. A risk rating for each finding (high, medium, low) with the reasoning behind it. Mandatory rules: do not state that a licence, exemption, or reporting obligation applies in a given jurisdiction unless it is tied to a named statute or regulator guidance, flag it for local counsel confirmation instead. This is an analysis aid for a qualified lawyer to review, not a substitute for jurisdiction-specific regulatory advice.
Embedded Finance Partnership AgreementAgreementExpertDraft / Generate
You are drafting an embedded finance partnership agreement under which [FinTech] will provide [banking/lending/payment] services through [Platform's] application. Facts: the specific service being embedded, the customer journey (who the end customer contracts with), and the revenue model proposed between the parties. Deliverables, as sections of one agreement: 1. API integration: technical specifications, uptime commitments, and change management for API updates. 2. Revenue sharing: the fee split, payment timing, and reconciliation process between [FinTech] and [Platform's] business. 3. Regulatory responsibilities: which party holds the licence for the [banking/lending/payment] service, and which party is responsible for customer-facing disclosures. 4. Customer ownership: who owns the customer relationship, and any restrictions on either party marketing to the other's customers after termination. 5. Data sharing: what customer data passes between the parties, the permitted uses, and retention limits. 6. Liability allocation: how loss from a service failure, compliance breach, or data incident is split between [FinTech] and [Platform's] business. 7. Term, exclusivity if any, and termination, including transition assistance obligations. Mandatory rules: do not state which party bears a specific regulatory obligation unless it is tied to the licence [FinTech] or [Platform's] business actually holds, flag it for confirmation instead. This is a drafting aid for a qualified lawyer to review, not legal advice to either party.
Stablecoin Issuance FrameworkMemoEnterpriseCompliance / Due Diligence
You are preparing a legal framework memo for [Company], which is planning to issue a stablecoin in [jurisdiction]. Facts: the stablecoin's reserve asset composition, the redemption mechanism proposed, and the intended user base, retail, institutional, or both. Deliverables: 1. Reserve requirements: composition, custody arrangements, and any segregation obligations that apply in [jurisdiction]. 2. Regulatory classification: whether the token is likely to be treated as e-money, a security, a commodity, or a distinct stablecoin category under the regimes in scope, including MiCA and applicable state money transmission law where relevant. 3. Redemption rights: the terms on which a holder can redeem the token for the reserve asset, and any conditions or delays [Company] can lawfully impose. 4. Audit and attestation requirements: frequency, scope, and who must perform them. 5. Consumer disclosures: the risk warnings and reserve composition information [Company] must give holders before or at issuance. 6. A list of the specific regulations in scope, naming each one, with the obligation it creates for [Company]. 7. Open regulatory questions that need local counsel input before issuance proceeds. Mandatory rules: do not state that a specific regulation applies to [Company]'s planned issuance, or that a classification is settled, unless you name the provision it rests on, mark it for local counsel confirmation instead. This is a drafting aid for a qualified lawyer to review, not a substitute for regulatory advice.
Anti-Money Laundering PolicyPolicyEnterpriseDraft / Generate
Act as compliance counsel drafting a comprehensive AML/KYC policy for [financial institution/fintech company] operating in [jurisdiction]. Facts: the products or services offered [describe], the regulator with primary supervision [regulator], and whether the business has cross-border customers [yes/no]. Deliverables: 1. Customer due diligence procedures at onboarding, including identity verification standards. 2. Enhanced due diligence triggers: the specific risk factors that escalate a customer to enhanced review. 3. Suspicious activity reporting: the internal escalation path and the filing obligation to [regulator]. 4. Record-keeping requirements, including retention periods. 5. Staff training obligations: frequency, content, and who must complete it. 6. The governance structure that owns this policy, including the designated AML officer. Mandatory rules: cite the specific AML/KYC regulation or guidance of [jurisdiction] behind each threshold, retention period, and reporting deadline. Do not state a filing deadline or retention period as settled unless you can name the regulation it comes from; flag it for [financial institution/fintech company]'s compliance and legal teams to confirm before adoption.