Documentation & Setup

Learn how to configure SyncroGate between Stripe and Lexware Office or sevdesk in just a few minutes.

1. Generate Lexware Office / sevdesk API Key

SyncroGate requires write permissions for your accounting system to generate receipt vouchers either as drafts or finalized records (live mode).

Log into your accounting platform.
For Lexware Office: Navigate via the gear icon in the top right to Extensions → Public API and generate a new key.
For sevdesk: Click on Settings → Users at the bottom left, select your account name, and click Show API Token.
Copy this key and paste it into the SyncroGate dashboard under Settings → Integrations.

2. Configure Stripe Webhook

Stripe notifies SyncroGate in real time whenever payments succeed or refunds occur. An endpoint webhook must be configured for this purpose.

Log into the Stripe Dashboard and navigate to Developers → Webhooks.
Click Add destination / Add endpoint.
Under events to send, select the following events: checkout.session.completed, invoice.paid and charge.refunded.
The API version does not need to be changed.
Enter the Webhook URL displayed in your SyncroGate dashboard.
Save the webhook by clicking Add endpoint.
Reveal the Signing secret (whsec_) and paste it into your SyncroGate dashboard.

3. Supported Stripe Events

checkout.session.completed

Triggered when a customer successfully completes a one-time purchase or a new subscription checkout flow.

invoice.paid

Triggered when a recurring billing invoice (subscription renewal) is successfully captured.

charge.refunded

Automatically creates a credit note / refund voucher in Lexware Office or sevdesk whenever you initiate a refund in Stripe.

4. Reliability (Idempotency & Queues)

SyncroGate operates on a resilient serverless architecture. When a webhook payload is received from Stripe, it is immediately persisted as Pending in our PostgreSQL database (idempotency guarantee).

If the target accounting system is temporarily unavailable due to rate limits or maintenance windows, our background queue steps in. The pipeline executes automatic retries using exponential backoff up to 5 times to prevent data loss. You can monitor the ingestion lifecycle inside your dashboard Event Audit Trail and trigger manual retries if needed.