Stripe Billing / Invoicing integration

Connect from Bookkeeping → Integrations → Stripe Billing / Invoicing using a merchant-created restricted API key. Confirm the detected Stripe business before saving. Invoice import starts enabled. Payment recording and MakePay notifications start disabled.

Create a restricted key

In the intended Stripe business, open Developers → API keys → Create restricted key. Use a dedicated live restricted key (rk_live_…). Allow read access to the current account information and invoices. To enable payment recording, also allow invoice writes and event reads. The connection uses these endpoints:

• GET /v1/account to confirm the business and default currency.
• GET /v1/invoices and GET /v1/invoices/{id} to import and refresh invoices.
• GET /v1/events and GET /v1/events/{id} to verify a recorded MakePay payment.
• POST /v1/invoices/{id}/pay, always with paid_out_of_band=true, for an already-confirmed MakePay payment.

See Stripe's restricted-key guide. Invoice-write access is needed only when you choose payment recording. Other resources can remain disabled. Stripe may report a missing permission by its Dashboard label; use the request logs to check the exact rejected endpoint. MakePay checks the event-read permission when you enable payment recording. No MakePay OAuth application or Stripe Connect registration is required.

Enter the key, select Check API key, confirm the detected business and choose its Stripe billing account. The native Stripe account is retained as the payment's account context. Save the options you want. This connection accepts live restricted keys; unrestricted secret keys and test keys are not accepted here. The key is encrypted with the MakePay company/connection context and is never returned in a connection summary.

Invoice payments

Enable Accept and record MakePay invoice payments to share payment links from eligible imported invoices. Checkout supports live, open invoices using send_invoice collection with auto_advance=false and no scheduled payment attempt. Configure these collection settings in Stripe before sharing a MakePay link. MakePay rereads the invoice before checkout and before recording the payment.

Stripe API values use the currency's minor unit. The connection handles the published zero-decimal currencies and invoice-specific ISK/UGX, HUF and TWD rules. Three-decimal accounting currencies are currently unsupported; connection or sync stops for review instead of guessing a conversion. Draft, void, uncollectible, test-mode, account-configured customer and Connect/on-behalf-of invoice contexts cannot accept MakePay checkout through this connection.

Once a MakePay checkout is confirmed, MakePay asks Stripe to record the payment as received outside Stripe. The request always sets paid_out_of_band=true, which tells Stripe to make no charge. It does not initiate a Stripe card payment or payout. Stripe sets the payment's processing timestamp; the original settlement remains available in MakePay. Stripe's independently configured email and automation rules still apply.

The exact invoice balance must match immediately before the request. Recovery then requires an invoice.updated event carrying that request's unique idempotency key, the same invoice/customer/currency, and previous amounts proving the exact MakePay amount was applied. The current invoice must agree. A final paid balance alone is insufficient: concurrent partial payments, credits or mismatched event evidence remain in review.

Sync, recovery and notifications

Full invoice scans run in bounded batches about every five minutes, using Stripe's creation-order cursor. Larger accounts take multiple runs. Scans repeat to refresh balances and voids. The panel displays the most recent 100 imported records. Sync requests another batch.

Before dispatch, MakePay stores an immutable request and unique reference. An uncertain request is never blindly posted again, even after Stripe's minimum 24-hour idempotency retention expires. Recovery checks the original event and invoice. Delayed events can be recovered on a later run. Searches are bounded to the request's time window and five pages; missing, duplicate, incomplete or expired evidence requires review. Stripe retains events for 30 days; automatic search stops conservatively after 29 days. Use the displayed request reference and Stripe request logs when reviewing an uncertain result.

Payment-recorded and sync-problem notifications are optional, in-app and deduplicated. Turning payment recording off pauses unpaid MakePay links. Already-confirmed checkouts remain eligible for reconciliation. A different Stripe business requires disconnecting first. Rotating the restricted key for the original business and currency preserves invoice links and history.

Wallet expense export, receipt uploads, automatic invoice creation and invoice-note updates are unavailable through this connector. Local protocol fixtures and simulated settlements are not a live Stripe-account round trip; that requires merchant credentials.