Everything up to here worked without a brand domain or a payment account. Real end users sign in on a domain of yours, and real customers pay you, not ShipRev. This page covers both.
Your brand domain
End users sign up and sign in on your application's brand domain, for example account.example.com. The region picks your application from the host name of each request, so the domain must be verified first.
In the operator console, under Settings, Customer sign-in:
- Add the brand domain.
- Publish the TXT record the console shows in your DNS.
- Verify it. How long that takes depends on your DNS provider; it does not hold up anything you did on the previous pages.
The record the console shows has this form, for the brand domain account.example.com:
| Field | Value |
|---|---|
| Type | TXT |
| Name | _shiprev-challenge.account.example.com (in many DNS providers, _shiprev-challenge.account) |
| Value | shiprev-verify= followed by 48 hexadecimal characters, exactly as the console shows it |
If verification fails, When verification fails lists the usual causes.
Choose how end users sign in
Once the domain is verified, the hosted sign-in page and the customer portal work with the default settings: end users sign in on your brand domain and land in the portal, with their subscription, billing, usage and members. One setting is off by default and must be on before your first end users arrive, including the ones you invite: Allow self sign-up, under Settings, Project, Customer sign-in. Until it is on, no new account can be created; see Who may create an account.
To send end users back to your own application instead, or to put the sign-in page in your own product with the React components, see Hosted pages, components or your own. Whichever way you choose, your backend checks every request with the Server SDK as in Backend.
Connect the account you are paid into
Customers pay you, not ShipRev. Charges are made on your Stripe account, and ShipRev adds no application fee to them.
In the operator console, open Settings, Payment Gateway; the application's page in the developer console links to it as Payment settings. Save your Stripe secret key, register the webhook address the page shows as an endpoint in your Stripe Dashboard, and save the endpoint's signing secret. Take payments on your own Stripe account has the steps and the events the endpoint must send.
Once connected, publishing a plan version creates its product and price on your Stripe account, and end users check out on it. Rehearse with a test-mode key and Stripe's test cards first; Test mode and going live covers the switch.
Before you charge the first customer
- The brand domain is verified and reachable.
- Allow self sign-up is on.
- A real end user can sign in and sees the plans you published.
- The payment connection uses your live key, or you are deliberately still in test mode.
- Your backend's guarded routes refuse a used-up allowance the way you expect, as rehearsed in A subscription in test mode.