Payment Links now support local pricing in multiple presentment currencies instead of USD only. Merchants can choose one supported pricing currency when creating a Payment Link, then use that currency consistently for product prices, order totals, and link displays. This capability is designed for merchants who want market-specific pricing across Europe, Southeast Asia, the Middle East, Japan, Korea, Latin America, and other international business flows. It makes Payment Links easier to manage in the Merchant Portal while keeping the payer journey familiar. Payment Links currently uses the same pricing-currency coverage as Stablecoin Checkout.Documentation Index
Fetch the complete documentation index at: https://docs.stablepayfi.ai/llms.txt
Use this file to discover all available pages before exploring further.
When to use it
This feature is especially useful when you want to:- Price Payment Links directly in local fiat currencies instead of USD.
- Sell across multiple countries or regions with pricing that matches local expectations.
- Use Payment Links for courses, services, events, digital goods, or lightweight commerce.
- Keep original pricing currency visible across the Portal, list views, detail views, and payment drawer.
Supported pricing currencies
The current documented coverage includes:- Default: USD
- Europe and North America: EUR, GBP, AUD, CAD
- Asia-Pacific: JPY, HKD, SGD, KRW
- Southeast Asia: IDR, PHP, VND, THB, MYR
- Latin America: MXN, BRL
- Middle East: AED, SAR, QAR, KWD, OMR, BHD
Minimum order totals and decimal precision
Payment Links validates both the minimum order total and decimal-precision rules for the selected pricing currency. The table below reflects the currently documented configuration:| Currency | Minimum order total | Decimal places |
|---|---|---|
| USD | 0.10 | 2 |
| EUR | 0.10 | 2 |
| GBP | 0.10 | 2 |
| AUD | 0.20 | 2 |
| CAD | 0.20 | 2 |
| JPY | 20 | 0 |
| HKD | 1.00 | 2 |
| SGD | 0.20 | 2 |
| KRW | 200 | 0 |
| IDR | 2,000 | 0 |
| PHP | 10.00 | 2 |
| VND | 3,000 | 0 |
| THB | 5.00 | 2 |
| MYR | 1.00 | 2 |
| MXN | 2.00 | 2 |
| BRL | 1.00 | 2 |
| AED | 0.50 | 2 |
| SAR | 0.50 | 2 |
| QAR | 0.50 | 2 |
| KWD | 0.050 | 3 |
| OMR | 0.050 | 3 |
| BHD | 0.050 | 3 |
- These thresholds are Payment Link creation-side minimum order totals, not the underlying blockchain payment minimum.
- For multi-item Payment Links, StablePay validates the order total as a whole rather than checking each item separately.
- Decimal precision rules change together with the selected Payment currency.
How it works
- A merchant creates or edits a Payment Link in the Merchant Portal.
- In the Products area, the merchant chooses one Payment currency. The default is USD.
- All products in that Payment Link use the same pricing currency.
- StablePay validates price formatting, order totals, and minimum creation amounts for that currency.
- After the link is created, the original pricing currency is shown in list views, detail views, Preview, and the payment drawer.
- Customers still complete payment through the existing StablePay hosted checkout flow.
Core rules
One Payment Link uses one pricing currency
All products inside a single Payment Link must use the same pricing currency.- Payment currency is configured once at the Payment Link level.
- New products inherit the current Payment currency automatically.
- Mixed-currency products are not supported inside the same link.
- If mixed currencies are submitted, the system returns a validation error.
Minimum order amounts are validated at the order-total level
Minimum amount validation is based on the minimum order total, not on each product separately.- Standard products contribute
unit price × quantity. - If a product supports adjustable quantity, StablePay uses
unit price × minimum quantityto calculate the minimum order amount. - The Payment Link can be saved only when the order total meets the configured minimum for that currency.
Decimal precision follows the selected currency
Different currencies support different decimal precision, and both frontend and backend validation apply.- Zero-decimal currencies such as JPY, KRW, VND, and IDR do not allow decimal amounts.
- Common fiat currencies such as USD, EUR, and HKD typically allow 2 decimal places.
- Currencies such as KWD, OMR, and BHD allow 3 decimal places.
What merchants gain
| Capability | Description |
|---|---|
| Local-market pricing | Create Payment Links in the fiat currency that matches the market being served. |
| Single-currency consistency | Keep all products in one link under one pricing currency. |
| Clearer list and detail displays | Show the original pricing currency in Price, Header, Products, and payment drawer views. |
| Consistent validation | Apply minimum order amount and decimal-precision rules based on the selected currency. |
| Stronger historical records | Preserve the presentment currency and amount snapshot for completed payments. |
Rules for editing existing Payment Links
Payment currency is not always freely editable after a link is created.- Historical Payment Links are treated as USD by default for compatibility.
- If a Payment Link has no successful payments yet, its Payment currency can still be changed.
- Changing the currency does not automatically convert price numbers using an exchange rate. Merchants should review pricing manually.
- After a currency change, StablePay revalidates the link using the new currency’s minimum order amount and decimal rules.
- If the Payment Link has already received a successful payment, the currency can no longer be changed. Create a new Payment Link to use another currency.
What this iteration does not include
This update does not include:- Multi-currency products inside the same Payment Link.
- Buyer-side currency switching on hosted checkout.
- Automatic local currency selection based on IP or browser language.
- Merchant-defined exchange rates.
- Subscription-style Payment Links.
- Changes to the core hosted checkout payment flow.
Important notes
- If no currency is explicitly selected, StablePay defaults to USD.
- Minimum order amounts are system-configured thresholds and are not the same as the underlying blockchain minimum payment amount.
- Save-time validation still happens on the backend even when the frontend already shows guidance.
- If you aggregate metrics across links with different currencies, avoid adding GMV values together without a currency-normalized view.
