Compare package allowances and optional one-time purchases, review the charge currency and keep licences with the correct workspace.
Package allowance or optional purchase?#
Your package defines how many apps, users and how much storage this workspace can use. An optional one-time licence unlocks the specifically named app, theme or feature for this workspace. It does not add app slots, staff seats or storage, and does not change the package advertising rules.
Included apps and themes do not require a separate purchase. Optional paid items show their price before you buy. A future feature marked unavailable cannot be purchased merely because its name appears in an administrative catalogue.
| Choice | When it fits | What it changes |
|---|---|---|
| Included app or theme | Use a capability covered without an extra licence charge. | Install the app within package limits and complete its prerequisites, or select the included theme. |
| One-time paid add-on | Unlock the named optional item for one workspace. | The owner reviews a separate charge. Verified payment grants the licence; normal package and dependency rules still apply. |
Check which workspace owns the purchase#
Confirm the workspace name and personal/corporate profile before approving payment. Licences belong to that workspace and do not transfer when you switch profiles or use another company account. A staff invitation does not bring a personal licence into the company.
Only the workspace owner can authorize the purchase. App administration and installation remain subject to the existing owner/admin permissions. A licence is retained when the app is disabled, so reinstalling in the same workspace does not require buying the same licence twice.
Review the actual charge currency#
Choose an offered payment currency and review the exact one-time amount before creating the purchase. The currency shown is the charge currency sent to Airwallex. Countries without an offered local currency start in USD. Changing interface language does not change a locked invoice or recurring subscription currency.
The listed launch currencies are USD, SAR, AUD, GBP, EUR, CAD, AED, QAR and KWD. These are documented Airwallex Billing currencies; actual payment availability still depends on the configured Emnaro merchant account and supported payment method. An unavailable provider closes checkout rather than substituting AUD or another currency.
An accepted purchase retains its price/currency snapshot. A later catalogue or exchange-rate update does not silently rewrite the existing invoice. Your card issuer can apply its own conversion or fees.
Complete payment and verify access#
Creating a purchase prepares an Emnaro billing invoice and its hosted payment workflow. It is separate from invoices that your business sends to customers. Review the amount before continuing to Airwallex. A browser return or a screenshot is not payment confirmation.
The licence is granted only after the provider-verified invoice and payment match the original workspace, merchant configuration, currency, amount and production environment. Pending or unknown payment outcomes retain the original purchase so retrying does not create another charge.
When payment is verified, return to the original app or theme selection. Installing a licensed app still needs available app allowance and its prerequisites. Buying a theme does not install Ecommerce or silently configure a store. Refund or disputed-payment handling requires the supported billing/support workflow; a credit or support message does not itself prove that funds were returned.
- Confirm the active workspace and selected item.
- Review one-time price, currency, prerequisites and package allowance.
- Authorize the purchase, then explicitly continue to the hosted payment page.
- Wait for verified payment status before enabling the paid item.
- Keep the invoice and licence reference in the workspace.
Evaluate in the isolated demo#
The disposable demo can show and evaluate available optional capabilities without making a live purchase. Its evaluation access is not a paid production licence and ends with the demo workspace. An expired demo or a second profile cannot extend that access.
Previewing a storefront theme uses fictional products and does not prove payment or add merchandise to your store. Future white-labelling or branded SMTP entries remain unavailable until their actual capability and server-side entitlement checks are released.
Publish a price deliberately#
In master administration, open Add-on pricing and choose a released app or theme. Enter the one-time USD base price, review the item and included-versus-paid choice, and save its versioned configuration. The system initially treats the existing apps and themes as included.
Publishing a first fee preserves existing installed app access or the currently selected theme through the grandfathering policy. New selections follow the new catalogue price. Do not use a fee change to retroactively invoice a customer or imply that a future capability already works.
All currently supported add-on purchases are one-time charges. Recurring SMTP usage, external provider fees, metered services or new subscription products require their own separately specified billing policy and readiness checks.
Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.