Getting started with Stripe as a payment provider

Historical retrospective - January 2026 This article was written afterwards and describes the feature as it worked during the stated period.

Stripe as a payment gateway and Stripe Billing import are separate features. Connect Stripe, check its status, and select it on plans that should offer card payments. Test checkout and follow the approved payment status; a technical confirmation alone does not prove money moved. Use the separate import flow when customers and subscriptions must be moved. See the current guide (Markdown file, AI agent-friendly)

Gateway or import

Use the gateway status and the import’s own preview separately. A customer already in Alunta should not be recreated merely because Stripe is connected. The first test should check plan, currency, and card status with synthetic data.

Prerequisites

Stripe must be connected and ready, and the plan must have a price in the currency used by checkout. Select Stripe on the relevant plan, open checkout, and run a small synthetic test. Check card, payment, and any invoice status in the order shown.

If you also import

The gateway connection does not turn existing Stripe Billing customers into Alunta customers. Import must be previewed and confirmed separately. Do not use an import as a gateway test; the two flows have different outcomes and review points.

A safe first review

Confirm that the plan is available for sale, its currency has a price, and checkout shows the payment information intended by the team. Do not use real card data in a historical test article. After checkout, check subscription, invoice, and payment separately. If a payment is pending, let its status flow finish rather than creating a manual payment in parallel.

The import article is relevant only once the gateway is ready and existing Stripe records can be read. Plan matching is required; a Stripe plan without a corresponding Alunta price should remain unprocessed.

FAQ and boundaries

The Stripe gateway applies to Alunta payments after connection and plan selection. It does not automatically change old payments. If the goal is moving Stripe Billing, review matching, price, interval, and renewal before commit. If the goal is only card payments, stop after a successful gateway test and do not import data.

Support scenario

A team using both the Stripe gateway and import should keep the two test datasets separate. Gateway testing concerns a new purchase; import testing concerns existing records and matching. Check both results before telling a customer Stripe is ready.

Check after the action

Use this check during follow-up: note what was visible before the action, perform only the selected action, and check the document or mandate afterwards. Read a status again before informing the customer if it changes later. The retrospective describes the documented milestone; the current guide and interface determine today’s steps. Examples use fictional customers, amounts, and dates.

If the result differs

If the result does not match expectations, keep the visible status and investigate the relevant prerequisite instead of repeating the action blindly. Check currency, date, customer, payment method, and whether the document was already sent or booked. When answering a customer, distinguish what the system recorded from what the bank or recipient has not yet confirmed.