Skip to main content

​
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.
Test mode does not block outbound emails. If an action normally sends an email in production, Hyperline also sends it from your test account to the configured recipient, such as a customer email, invoice email, checkout recipient, quote recipient, or additional email recipient. Use internal or dedicated test email addresses for sandbox customers and recipients unless you intentionally want a real recipient to receive the message.

​
Testing payments

Test payment flows before using production bank accounts or payment provider accounts. You can use test card numbers and test bank account numbers as described below.

​
Testing credit card numbers

To test payments in Hyperline, you can use the false credit card numbers provided by Stripe or Mollie (see section below). Payment providers supply test card numbers for payment tests. You can find testing card numbers on the following pages:

​
Testing direct debits

You can test direct debits with test account numbers provided by most payment providers. You can find testing numbers you can use for Stripe on this page.

​
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.
Click Create new events when you are ready.The events can take a few seconds to be ingested.They will appear in your customer’s Events page.You can easily delete them in the Events page afterward.
You are done. You can now create your first usage-based plan based on these events.