Skip to main content
A standalone environment, kept apart from your live production data To try out Ruba or build out your integration without stressing over real money movement or damaging your live organization, you can use our testing environment. It is a dedicated server, fully separated from the production instance, where you can run as many experiments as you like.
Why a separate environment instead of a test mode?Because we handle money and must account for every movement to maintain our Merchant of Record service, we found it safer to wall off live data from test data so they never mix. On top of that, it lets you spin up an unlimited number of accounts and organizations to try out plenty of scenarios. Treat it as your personal development server!

​
Getting underway

You can reach the testing environment directly at sandbox.getruba.com or by clicking Go to sandbox inside the organization switcher. After that, you will need to set up a dedicated user account and organization, following the same steps outlined in our Quick Start guide.

​
Trying out payments

The testing environment lets you walk through the entire customer journey, including checkout. You can run test payments using Stripe’s test card numbers. The simplest way to simulate a successful payment is to use the card number below with a future expiration date and a random CVC:

​
API and SDK

To send requests to our API, all you need to do is point the base URL away from https://api.getruba.com and toward https://sandbox-api.getruba.com. You will also have to generate an access token inside the testing environment, since a token created in production cannot be used in the sandbox. Our official SDK supports the testing environment via a dedicated parameter.

​
Known caveats

The caveats below apply solely to the sandbox and do not reflect the production behavior.
  • Customer-facing emails (order confirmations, subscription renewal reminders, and so on) are only sent to recipients who belong to your organization. Manage these in Settings → Members. Sub-addressing aliases like you+test@example.com are allowed.