Localization
What can be localized today and where RevKeen checkout is still English-first
RevKeen checkout is currently English-first. RevKeen does not yet expose a public locale parameter or full built-in translation controls for hosted checkout labels.
What You Can Localize Today
- Product names and descriptions shown in checkout
- Link names and campaign copy around checkout
- Success and cancel destinations
- Your terms, privacy, and support links
- Currency and tax configuration for the offer you send the customer to
Recommended Pattern
If your application supports multiple languages today:
- Detect language before the customer reaches checkout.
- Send the customer to the localized offer, product copy, or payment link you want them to see.
- Return them to localized success and cancel pages.
- Keep legal links, pricing copy, and tax presentation aligned with that locale.
What Is Not Available Yet
- A documented checkout
localeparameter on payment links or checkout sessions - Browser-language auto-detection for hosted checkout labels
- Full translation of RevKeen-controlled labels, placeholders, and system copy
Practical Workarounds
- Create separate localized landing pages that each route into the correct checkout flow.
- Localize your product catalog copy so the hosted page reflects the right product text.
- Use localized success pages to continue the post-purchase journey in the customer's language.
- Keep one checkout per offer or locale when you need strict control over surrounding copy.
Related
- Checkout Links -- Reusable hosted purchase URLs by locale or campaign
- Checkout Sessions -- Backend-created localized routing patterns