Getting Started

StablePay’s current product capabilities are divided into two main lines:

• Pay In: Collecting payments from customers, including hosted checkout, invoicing, payment links, SaaS platform integrations, and subscription billing.
• Pay Out: Disbursing funds to external wallets or another StablePay Account.

Start here: Register for StablePay Portal

​

Recommended Onboarding Path

1. Complete merchant registration via the StablePay Portal.
2. Determine whether your primary need is Pay In, Pay Out, or both.
3. Select the appropriate product path based on your business scenario.
4. Complete StablePay KYB and await capability review and activation according to product requirements.
5. Complete optional configurations such as branding and notifications.
6. Test critical business processes before going live.

​

Self-Service Registration

StablePay supports merchant self-service registration. After registration, merchants can log in to the Merchant Portal to select products, submit KYB, test workflows, and gradually activate required capabilities.

​

Choose the Right Product

​

Pay In

When you need to collect payments from customers, start with these products.

​

Pay Out

When you need to send funds out, start with these products.

​

Other Capabilities

​

Common Scenarios

​

Product Selection Matrix

​

Capability Activation Notes

• Stablecoin Checkout, Invoicing, Payment Links, SaaS Platform Integration, and Stablecoin Subscriptions belong to the Pay In path.
• Payout to Wallets and Payout to StablePay Account belong to the Pay Out path and may require merchant approval, balance configuration, and rollout activation.
• Corporate Cards requires merchant registration, KYB completion, and review by the StablePay merchant team for activation.
• If your business involves higher limits, fiat capabilities, or additional compliance requirements, we recommend completing formal KYB verification as soon as possible.

​

Optional Configuration Steps

​

Checkout Payment Settings

StablePay now supports merchants configuring checkout payment strategies centrally in Merchant Portal > Settings > Payments. These configurations apply to StablePay hosted checkout scenarios, including Stablecoin Checkout, Payment Links, and invoice checkout where applicable. Note that these settings only affect newly created checkout sessions or subsequently triggered hosted payment pages, and will not retroactively modify already created sessions.

​

1. Default Payment Method

You can now configure the default payment method priority for checkout:

• Wallet selection
• Transfer to Pay

If your customers more frequently use direct wallet connections, you can keep wallet priority; if your customers more frequently pay via transfer addresses, you can switch the default entry to Transfer to Pay to reduce additional user switching steps.

​

2. Transfer Default Network and Currency

When the default payment method is set to Transfer to Pay, merchants can further set the default displayed network and currency to help customers directly enter the most suitable transfer path.

• Configurable default network
• Configurable default displayed currency
• Different networks support different currency ranges; for example, TRON currently only supports USDT

​

3. Checkout Session Expiration Time

Merchants can now uniformly set the default expiration time for hosted checkout:

• Minimum 30 minutes
• Maximum 24 hours
• Takes effect as the merchant default value
• If merchants create checkout sessions via API, they can still override individually via expires_in

This setting applies to the checkout session lifecycle shared by Wallet Pay and Transfer to Pay.

​

4. Transfer to Pay Underpayment Tolerance Settings

Transfer to Pay underpayment tolerance now supports separate configuration by business scenario:

• Checkout configured separately
• Invoicing configured separately

Merchants can choose:

• Require full amount received
• Allow underpayment success proportionally
• Allow underpayment success by fixed amount

Unless using full amount received logic, merchants need to self-assess the risk of fulfillment loss that underpayment may bring.

​

Checkout Tolerance Example

When configured by percentage, you can define the minimum receipt requirement as a percentage of the order amount. When configured by fixed amount, you can define the fixed difference amount allowed for underpayment.

​

Invoicing Tolerance Example

Invoice checkout underpayment tolerance can be configured independently from Checkout, suitable for merchants accepting small tail differences in B2B billing scenarios.

​

Trial Limits and Business Scenario Restrictions

If a merchant has not yet completed KYB verification, certain fund-related scenarios will be restricted according to trial limits. After completing KYB, merchants can use corresponding capabilities according to their formally reviewed and approved configuration.

​

Pre-Integration Recommendations

• First review Supported Wallets and Supported Networks.
• If you use non-USD pricing, review Currencies & Auto Currency Conversion.
• If you plan to accept payments via platform stores, first review SaaS Platform Integration.
• If you plan to use Pay Out, first review Payout to Wallets and Payout to StablePay Account.
• If you plan to use Corporate Cards, first review Corporate Cards.
• If you want hosted pages to display your brand, first complete Branding Settings.
• Before going live, confirm Compliance and Regional Availability.