Accepting crypto or stablecoin payments involves more than generating a wallet address.
For an enterprise payment operation to scale, payments must be matched accurately to orders, funds must be consolidated and settled efficiently, payment discrepancies must be handled consistently, and every transaction must move through a clear and auditable compliance process.
Cregis Payment Engine addresses these operational requirements through digital asset collection, smart settlement, payment discrepancy handling, compliance screening, and API integration.
It is not an isolated checkout tool. It is an important product within Cregis' enterprise digital asset infrastructure. Cregis' broader capabilities span WaaS wallet infrastructure, Rails fund flow orchestration, and Custody, helping enterprises build digital asset collection, payout, fund operations, and asset management capabilities.
Why Enterprises Need a Dedicated Crypto Payment Engine
The difficult part of enterprise digital asset payments is not completing a single blockchain transaction. It is managing large volumes of orders, addresses, assets, networks, and compliance requirements on a continuous basis.
When businesses rely only on receiving addresses or a patchwork of point solutions, operational complexity shifts to finance, operations, customer support, and engineering teams. As transaction volume increases, manual consolidation, reconciliation, refund processing, and risk investigation can quickly become bottlenecks.
A mature enterprise digital asset payment engine should answer several practical questions:
- How is an incoming payment matched to the correct order?
- How are funds consolidated across networks and addresses?
- How are different incoming assets converted into the preferred settlement currency?
- How are underpayments, overpayments, and refunds handled?
- How are transaction and address risks identified before settlement?
Cregis Payment Engine brings these functions into a connected workflow, helping businesses expand stablecoin and digital asset payment activity without losing operational control.
Multi-Asset Acceptance and Smart Settlement
Cregis Payment Engine accepts major assets including BTC, ETH, USDT, and USDC, as well as additional digital assets.
The platform can consolidate payments received across different networks into the merchant's preferred settlement currency. This reduces the amount of manual conversion, fund consolidation, and reconciliation required across multiple assets and blockchain networks.
Real-time processing and T+0 settlement also give businesses faster visibility into available funds, supporting working-capital efficiency in cross-border and high-volume payment environments.
Cregis' underlying wallet infrastructure currently supports more than 40 blockchain networks and over 85 tokens. The precise assets and networks available within an individual Payment Engine deployment depend on the merchant scenario, settlement configuration, and compliance requirements. Businesses can also apply to add tokens that are not yet included in the standard list. View supported networks and tokens
Automated Handling of Payment Discrepancies
Real-world payment amounts do not always match the exact order value.
Cregis allows businesses to configure tolerance thresholds and define how underpaid or overpaid orders should be handled. Depending on the asset and merchant configuration, the system can request an additional payment, initiate a partial refund, or move the order into a full-refund process.
This automation does more than reduce customer support tickets. It limits the time finance, operations, and engineering teams spend investigating the same blockchain transaction and creates a more standardized, traceable process for payment exceptions.
Embedded AML, KYT, and KYA Controls
Enterprise digital asset payments require a balance between transaction speed and risk control.
Cregis Payment Engine includes AML screening alongside Know Your Transaction, Know Your Address, automated risk monitoring, and alerts. Embedding these controls within the payment workflow helps businesses identify transaction and address risks earlier and reduces the need to reconstruct evidence across disconnected systems after settlement.
No technology platform replaces a company's own licensing analysis, customer due diligence, or jurisdiction-specific compliance responsibilities. Product, compliance, and legal teams should confirm screening rules, risk thresholds, data-retention requirements, and escalation procedures before deployment.
API and SDK Integration
Cregis provides APIs and SDKs that allow businesses to embed digital asset payments into applications, websites, POS systems, and existing payment workflows.
Developers can build tailored experiences around order creation, payment status, callbacks, refunds, settlement, and reconciliation. Operations teams can manage payment status and exceptions through a more consistent workflow.
This model is particularly relevant to payment service providers, cross-border payment companies, forex brokers, fintech platforms, and businesses requiring white-label capabilities.
An implementation review should cover webhook behavior, order-state logic, permissions, reconciliation output, settlement rules, and responsibility for payment exceptions. API availability alone is not enough to determine whether a platform is ready for enterprise use.
When to Use Payment Engine or WaaS Sub-Addresses
For standardized order-based collections, Payment Engine provides a direct path to payment pages, order matching, payment discrepancy management, and settlement.
Payment Engine is generally the more suitable option for businesses that need to launch digital asset payments quickly and manage orders, payment status, refunds, and settlement through standardized interfaces.
As transaction volume, receiving-address requirements, or account structures become more complex, collecting payments through Cregis WaaS sub-addresses may provide a more mature underlying architecture.
In addition to operating scale and collection model, the capabilities of the company's internal technical team are an important consideration.
Payment Engine already provides standardized functionality for orders, payment status, callbacks, payment discrepancies, and settlement. The company's technical team mainly needs to handle system integration and connect the payment workflow to existing business systems. Compared with WaaS sub-address collection, Payment Engine generally requires less internal development and ongoing maintenance.
WaaS sub-addresses provide more fundamental wallet and address capabilities, but they also require a stronger internal technical team. The business will typically need to design and maintain address lifecycle management, customer or order mapping, on-chain transaction monitoring, callback processing, fund consolidation, reconciliation, exception handling, system monitoring, and security controls.
| Approach | Best suited for | Technical requirements | Primary value |
| Payment Engine | Standard order payments, faster deployment, and businesses requiring established discrepancy and settlement workflows | Primarily requires API, callback, and existing system integration, with relatively lower internal development and maintenance requirements | Unifies orders, payments, refunds, and settlement |
| WaaS sub-addresses | Large address volumes, complex account structures, and businesses requiring customized collection and fund operations | Requires a stronger internal technical team to build and maintain address management, transaction monitoring, account mapping, consolidation, reconciliation, and exception workflows | Provides greater flexibility across addresses, accounts, permissions, and underlying fund management |
Payment Engine and WaaS sub-addresses are designed for different collection models.
Businesses should select the approach that best fits their peak order volume, address scale, account structure, settlement assets, reconciliation requirements, compliance obligations, and the development and maintenance capabilities of their internal technical team.
Enterprise Security and Operating Scale
Cregis states that it has operated for nine years with zero security incidents. Its security architecture incorporates technologies including MPC and HSM, and the company reports certifications including ISO 27001 and SOC 2 Type II.
Cregis has served more than 4,000 businesses across over 50 countries and reports more than $300 billion in cumulative transaction volume. Its customer base spans financial institutions, payment providers, forex brokers, fintech companies, and Web3 businesses.
These figures do not replace technical, security, or compliance due diligence. They do, however, indicate that the infrastructure has been used across multiple markets and complex enterprise operating environments.
Payment Engine Pricing
Cregis Payment Engine charges a percentage-based transaction fee, with rates available from as low as 0.3%. Final pricing depends on transaction volume, supported asset and network combinations, settlement requirements, integration complexity, and the required level of service.
WaaS subscription pricing and Payment Engine transaction fees apply to different product capabilities. Businesses evaluating Payment Engine should focus on the transaction fee and implementation scope associated with payment processing, settlement, and exception handling rather than combining those costs with wallet subscription plans.
Frequently Asked Questions
Which digital assets does Cregis Payment Engine support?
Payment Engine supports BTC, ETH, USDT, USDC, and additional assets. Cregis' broader wallet infrastructure covers more than 40 blockchain networks and over 85 tokens. Businesses may apply for support for assets outside the current standard list.
How does Cregis handle underpayments and overpayments?
Businesses can configure tolerance thresholds. Depending on the order and asset type, the system can request an additional payment or trigger a partial or full refund workflow.
How much does Cregis Payment Engine cost?
Payment Engine uses percentage-based transaction pricing, starting from as low as 0.3%. The final rate depends on transaction scale, use case, and implementation scope.
What is the difference between Payment Engine and WaaS sub-address collection?
Payment Engine focuses on orders, payment processing, payment discrepancy management, and settlement, making it suitable for standardized order-based collections. WaaS sub-addresses provide address generation at scale, account mapping, wallet permissions, and underlying fund management, making them more suitable for businesses with large address volumes or customized collection workflows.
Should a company consider its technical capabilities when choosing between Payment Engine and WaaS sub-addresses?
Yes. Payment Engine provides standardized order and payment workflows, so the business mainly needs to complete system integration. It generally places lower demands on the internal technical team. WaaS sub-addresses provide greater flexibility, but the business will typically need to build and maintain its own address management, transaction monitoring, order mapping, fund consolidation, reconciliation, and exception-handling systems. This requires stronger internal development and ongoing maintenance capabilities.
Is Cregis simply a crypto payment gateway?
No. Cregis is an enterprise digital asset infrastructure platform spanning WaaS, Rails, and Custody capabilities. Payment Engine is an important product within this infrastructure, focused on digital asset collection and settlement.
Conclusion
Choosing an enterprise digital asset payment solution should begin with the actual flow of funds and operational responsibilities, rather than with the ability to generate a receiving address.
For standardized order-based collections, faster deployment, and payment exception management, Cregis Payment Engine connects digital asset collection, smart settlement, payment discrepancy handling, compliance screening, and API integration.
For businesses with large address volumes, complex account structures, or customized fund operation requirements, Cregis WaaS sub-addresses provide more flexible underlying wallet and address capabilities. However, this approach also places greater demands on the development and ongoing maintenance capabilities of the company's internal technical team.
Businesses should evaluate their primary assets and networks, settlement currency, peak order volume, address requirements, account structure, compliance rules, reconciliation needs, and internal technical capabilities before selecting either Payment Engine or WaaS sub-addresses.
Explore Cregis Payment Engine and request a solution assessment
About Cregis
Founded in 2017 and headquartered in Hong Kong, Cregis is an enterprise digital asset infrastructure platform.
Over the past nine years, Cregis has served more than 4,000 businesses across 50+ countries and regions, including crypto exchanges, fintech companies, payment providers, digital banks, brokers, and Web3 businesses.
Cregis provides a three-layer infrastructure stack spanning Wallet Infrastructure, Fund Flow Orchestration, and Custody Capabilities, enabling enterprises to manage the full lifecycle of digital assets, from asset control and fund operations to governance and compliance.
Its core products, Wallet-as-a-Service (WaaS) and Payment Engine, are widely used across enterprise digital asset use cases. As demand for digital asset infrastructure continues to expand globally, Cregis remains focused on helping businesses operate digital assets with greater control, lower operational complexity, and stronger compliance readiness.
