Hyperline test mode
Setting up billing often requires experimentation. Use test mode, also called sandbox, to test Hyperline without affecting your production account. When you switch to test mode, Hyperline creates a separate test account. You can create test customers, subscriptions, invoices, usage events, and payments before configuring production billing. Test mode has the same product capabilities as your production account. Use the product documentation to configure your product catalog, manage templates, send invoices, use credits and wallets, and more.Testing payments
Test payment provider and gateway flows in sandbox before connecting production bank accounts or production payment provider accounts. Sandbox payments use sandbox payment provider accounts, so no real money is charged or debited. If your sandbox account was populated from production data or from another billing system, existing production payment methods cannot be used in sandbox. Production cards, mandates, and bank authorizations are not compatible with sandbox payment provider accounts.Add a test payment method
To test automatic payments, add a test payment method to the sandbox customer from a hosted page:- Open a sandbox hosted page for the customer, such as a quote signature page, checkout page, invoice page, or customer portal.
- Go to the Add payment method section.
- Enter test payment details from your payment provider.
- Stripe test cards
- Stripe SEPA Direct Debit test details
- Adyen test cards
- Adyen SEPA Direct Debit: enter a test IBAN with a valid format. No money will be debited.
- Mollie test cards
Simulate usage data without code
This applies if you want to configure your first usage-based plan and assign a subscription to a customer in order to test Hyperline. In the test account, you can simulate usage data by generating fake events for a specific customer. This is done in two steps:1
Go to one of your customers from the Customer section
Then click the Events tab, and click Simulate new events.
2
Fill in the Event type field with the event name used to aggregate usage in your billing plan configuration.
Fill in:
- The event type (API calls, email sent, document retrieved or created, etc.)
- The date (leave blank if you prefer)
- The number of events to create
- You can optionally add extra parameters to your event with the JSON Payload field.

