Connect Qonto to Well

How Qonto stays secure with Well

Qonto authorises over OAuth, so Well holds no Qonto API key. The connection you approve carries these scopes: offline_access, organization.read, supplier_invoice.read, supplier_invoice.write, client_invoices.read, client_invoice.write, payment_link.write, webhook, attachment.read, card.read, client.read, einvoicing.read, insurance_contract.read, membership.read, payment_link.read, product.read, sepa_direct_debit.read, team.read, cash_flow_category.read, terminal.read, attachment.write, and cash_flow_category.write. webhook lets Qonto notify Well of changes. Well does not request the transfer-request, card, client, product, membership, team, bank-account or insurance-contract write scopes, so Well makes no transfer request and changes none of those records. Well does not request the payment, transfer, beneficiary or direct-debit write scopes, so Well makes no transfer. Twelve of the 22 are extra reads (attachment.read, card.read, client.read, einvoicing.read, insurance_contract.read, membership.read, payment_link.read, product.read, sepa_direct_debit.read, team.read, cash_flow_category.read, and terminal.read): they let Well answer questions about your attachments, cards, customers, e-invoicing settings, insurance contracts, members, payment links, products, direct-debit mandates, teams, cash-flow categories, and payment terminals, and they change nothing in Qonto. organization.read is what authorises the account side, so Well reads your organisation, bank accounts, balances, and transactions alongside your supplier and client invoices and their PDF attachments. supplier_invoice.write is used only by the send-to-Qonto action, which files one supplier-invoice PDF after you confirm it. client_invoice.write is used only for an invoicing change you ask for and confirm: a client invoice draft that you issue in Qonto, the send of an issued invoice as an e-invoice or by email, a quote, the removal of a payment reminder, the stop or restart of a recurring invoice, the paid status of an invoice, or the numbering mode. Well sends an invoice or a quote by email through Qonto only to the addresses on your customer's Qonto record, under a title Well writes from the document number, with Qonto's own email text and a copy to you; the card shows the title and each address before you confirm. payment_link.write is used only to create the card payment link of an issued invoice you ask for, and to turn off a link Well replaces; payment_link.read also lets Well check an expired link before Well replaces it. attachment.write is requested ahead of the receipt routine: Well attaches nothing to a Qonto transaction until you switch that routine on, and removes an attachment only when you ask and confirm. cash_flow_category.write is used only to change the cash-flow category of one transaction after you confirm it: Well assigns a category or subcategory, or clears it, and never creates, renames, or deletes a category. The older, separately approved Qonto write connector carries the same supplier_invoice.write grant. Apart from the cash-flow category change, none of these writes can mark a transaction, initiate a transfer, or create, lock, or change a card.