Kapta · 15/09/2026
The integration should track each billing cycle and relate it to the subscription, customer and corresponding document. Creating a subscription once does not cover subsequent renewals, plan changes and collection attempts.
How is this different from a one-off payment?
A subscription maintains a commercial relationship over time. Stripe documents events for subscription changes and collection outcomes. The connection needs events suited to your model and approved document trigger. Stripe subscription events.
Does creating a subscription mean the first payment succeeded?
Do not assume so. The documentation distinguishes subscription creation from payment and describes states requiring further completion. Check the applicable outcome before marking a cycle settled. Define document issuance separately from access to the service.
How should each renewal be identified?
Keep references for customer, subscription and billing cycle. An October payment must remain distinguishable from November even when customer and amount are identical. Use the source operation identifier rather than matching only email and amount.
What if collection fails and is retried?
Keep attempts linked to the original cycle. Your team should be able to see the outstanding situation and final outcome. When payment completes, recovery should not duplicate a document already prepared under company rules.
How should a plan change be tested?
Prepare a mid-period change, discount and end-of-cycle cancellation. Compare Stripe line items with the amounts expected in InvoiceXpress. Do not flatten every scenario into a fixed monthly fee when the source contains adjustments.
What should I send Kapta?
Your plans, billing periods, InvoiceXpress account and examples of successful and failed renewal. Explain how documents and service access are currently managed. The proposal should distinguish invoicing, customer communications and access management where those workflows are required.
