Transfer corporate funds without a key at
.
A payment API and operations dashboard for corporate cryptocurrency and stablecoin transfers. Using a 2-of-2 threshold signature scheme, UPBOND holds no signature elements (key shares) whatsoever. Rather than asking users to “trust us,” this non-custodial design makes the architecture itself the proof.
The ultimate question in corporate money transfer operations is, “Who holds the keys?” In a system where you have no choice but to trust the recipient, explanations—whether in audits or internal approval processes—ultimately boil down to an expression of trust.
UPBOND Wallet for Business addresses this question through its architecture. Signatures are generated using 2-of-2 threshold signatures (TSS/MPC), and the required shares are stored in the customer’s KMS or HSM. UPBOND operates only the policy gate and does not hold any signature elements. Therefore, even if an API key is compromised , it alone cannot be used to generate a signature.
Manage money transfer operations from a single screen
From submission to approval, signature, and transmission. You can manage approval queues, recipient lists, spending limits, audit logs for additional notes, and operator management—all from the same operational dashboard.
*This is a screenshot. The content shown is for illustrative purposes only and may differ from the actual UI.
A configuration that does not entrust keys serves as proof in and of itself.
Non-custodial status is guaranteed not by operational rules or commitments, but by the very structure of the keys. UPBOND does not hold any signature elements; only PolicyGate is responsible for operations.
. The required share is on the customer's side.
Signatures are generated using a 2-of-2 threshold signature (TSS/MPC). The required shares are stored in the customer’s KMS or HSM, and UPBOND does not hold any signature elements (key shares). UPBOND’s sole responsibility is to operate the policy gate, which determines whether a transaction complies with the policy.
- UPBOND does not have a signature element — it cannot complete a transaction on its own
- Mandatory shares are stored in the customer's KMS/HSM and are not transferred outside the system.
- Even if an API key is compromised, it cannot be used on its own to access the signature.
- It’s not about saying, “Trust us”—the structure itself serves as proof.
Businesses that do not have a signature element at
UPBOND does not hold any key shares. On its own, it cannot process any transactions.
The key remains within the customer's
management area
Mandatory shares are stored in the customer's KMS/HSM. The keys remain under the customer's control at all times.
Even if there is a leak, it does not reach the signature at
An API key alone is not sufficient for signing. The key configuration blocks access to the destination.
Proposal → Approval → Signature → Submission
The payment API operates as a state machine with these four states. Whether the operation is performed through the admin interface or via API integration with core systems such as ERP, the process is the same.
Proposal
Propose a transfer via the admin panel or API. The arrow list and maximum amount are determined here.
Approval
It is placed in the approval queue and will not proceed until the dual-control requirement is met.
Signature
2-of-2 threshold signature. The required share is located on the customer's KMS/HSM side.
transmission
It broadcasts the data and records the results and operation history in a dedicated audit log.
Through API integration with the admin panel and ERP systems, the system also supports unattended API signing (automated fund transfers). Even when automated, policy gates—such as the allowlist and amount limits—are still enforced on the server side.
Key Features
Money Transfer API and Operations Dashboard. It provides a comprehensive set of controls, record-keeping, and access management features necessary for daily money transfer operations.
Money Transfer API
A state machine with the following stages: Proposal → Approval → Signature → Submission. You can integrate fund transfers using the same API from both the admin console and core systems such as ERP.
PolicyGate
List of authorized recipients, maximum amount, and dual control. These policies are enforced on the server side.
Approval Workflow
Visualize requests in the approval queue. Since the process does not proceed to the signing stage until all required approvals have been obtained, a funds transfer cannot be completed with a single action.
Audit Log
Append-only. It records who approved what and when, as well as which transactions were signed and sent, in a way that cannot be altered later.
Operator Management
Register, grant permissions to, and suspend operators involved in money transfer operations. Changes to the organizational structure can be reflected directly on the operations dashboard.
Passkey Authentication
Instead of an email address and password, a passkey (biometric authentication) is used. Operations related to digital signatures are cryptographically linked to the individual user.
Just like the consumer version, it’s built on a production-ready infrastructure
UPBOND Wallet for Business is not a completely separate product built from scratch. It is built on the same authentication and operational infrastructure as the consumer version of UPBOND Wallet.
The consumer version of the UPBOND Wallet, a non-custodial wallet featuring patented secret key management, has a proven track record of over 1.03 million wallets in active use. The money transfer API and operational dashboard for businesses are built on the same authentication and operational infrastructure.
View UPBOND Wallet (Consumer Edition) →*As of July 2026; actual measurements taken on our own infrastructure
Charge
Since the optimal configuration varies depending on the volume of funds transferred, the approval process, and the systems we integrate with, we will provide a customized quote for each case.
We will provide personalized guidance based on the size of your remittance and your operational structure:
After reviewing the number of transactions, your approval process, the core systems to be integrated, and your key storage requirements, we will propose the optimal configuration and provide you with a quote. Please feel free to contact us for a consultation.
Click here to contact usAre you considering UPBOND Wallet for Business?
From key storage requirements and approval processes to integration with existing systems, we provide one-stop support—from requirements gathering to implementation design and cost estimates.