Branding
Show your logo, name and brand colour on checkout pages. Make one branding per store or product and pick it for each checkout link.
A branding puts your logo, name and colour on the checkout page instead of the Amboss look. Customers see your name in the header and your colour on the pay button, in both light and dark mode. A small "Powered by Amboss" note stays at the bottom.
- Brandings belong to your team, so sandbox and live share them.
- You can have up to 20, for example one per store or product.
- Each checkout picks one with
style_id. A checkout without one keeps the Amboss look.
In the API a branding is called a checkout style (payment.checkout_style).
What a branding has
| Field | Notes |
|---|---|
name | 1 to 60 characters. Only you see it, to tell your brandings apart. |
display_name | Up to 60 characters. Shown to customers next to your logo. |
brand_color | Hex colour like #ff0080, used for the pay button. The button text turns black or white, whichever is easier to read. |
logo_url | Set by uploading a logo. PNG, JPG or WebP, up to 512 KB and at least 128 by 128 pixels. |
Every field except name is optional. Leave one out and the page uses the Amboss default for it.
In the dashboard
- Go to Checkout in the sidebar and click Create branding.
- Set a name, display name and colour. The preview shows the checkout page in light and dark.
- Save, then upload a logo.
- When you create a checkout link, pick the branding under Branding.
We check the real file type of a logo from its contents, so renaming a file doesn't change what we accept. We also scan each logo before storing it and refuse ones that show violence, sexual content or self-harm.
Deleting a branding also deletes its logo. Checkouts that used it go back to the Amboss look.
With the API
Reading brandings needs a service API key with ENVIRONMENTS: READ. See API Keys.
For now, you can only create, change or delete brandings and upload logos in the dashboard. Those calls need a key for the whole team, and every API key is limited to one environment.
List brandings
find_many lists all your brandings. find_one(id) gets one.
query ListBrandings {
payment {
checkout_style {
find_many {
id
name
display_name
brand_color
logo_url
}
}
}
}Use a branding on a checkout
Pass style_id in the checkout input of create_receive. It must be one of your team's brandings.
mutation CreateBrandedCheckout {
payment {
transaction {
create_receive(input: {
wallet_id: "5e4b1e2a-9f3c-4a5b-8c7d-1234567890ab"
amount: "21000"
checkout: {
style_id: "3a5c7e9b-1d2f-4a6c-8e0b-2d4f6a8c0e1b"
success_url: "https://shop.example.com/orders/42/thanks"
}
}) {
id
checkout { id url style_id }
}
}
}
}The page shows the branding as it is when the customer opens the link. If you change a branding, open checkout links show the change the next time they load.
Next steps
Checkout Links
Send your customer a link to a hosted payment page. It shows the invoice, updates live when paid, and sends them back to your shop.
Lightning Addresses
Claim a Lightning Address like [email protected] so anyone can pay you from a Lightning wallet. Payments land in your wallet as normal receives.