Payment & Wallet Integrations
The payment and wallet integrations the JBM Market platform supports, so operators can offer funding and withdrawals to their own clients.
1. Introduction
This page describes the payment and wallet integrations the JBM Market platform supports, so operators can offer funding and withdrawal options to their own clients under their own licence.
JBM Market is a technology provider: we build and wire in these integrations. The operator running the platform is responsible for onboarding clients and for any handling of client funds under their own regulatory permissions.
2. Supported Payment Integrations
The JBM Market platform ships with cryptocurrency payment and wallet integrations, and can extend to further methods during delivery.
Supported cryptocurrency integrations may include, but are not limited to:
- Bitcoin (BTC)
- Ethereum (ETH)
- Tether (USDT)
- USD Coin (USDC)
- Other cryptocurrencies configured for the operator
Integrations that can be added on request include:
- Bank Transfers
- Credit Cards
- Debit Cards
- Third-party payment processors the operator works with
The set of available payment integrations can be updated as the platform evolves.
3. Deposit Flow Integration
3.1 Deposit Wallet Address
The platform can generate a deposit wallet address for each client inside the operator's branded client portal built on JBM Market.
3.2 Deposit Confirmation
Deposits are credited after the required blockchain network confirmations are completed.
Confirmation times depend on:
- Blockchain network congestion
- Cryptocurrency type
- Network transaction fees
3.3 Correct Network Usage
The flow surfaces the correct blockchain network for each transfer so clients select the right one.
Examples:
- USDT (TRC20)
- USDT (ERC20)
- USDT (BEP20)
Sending funds through an unsupported network may result in permanent loss, so the integration flags the required network clearly.
3.4 Minimum Amounts
Minimum amounts are configurable by the operator and displayed in the client portal.
4. Withdrawal Flow Integration
4.1 Withdrawal Requests
Clients submit withdrawal requests through the operator's branded client portal built on the JBM Market platform.
4.2 Security Verification
The withdrawal flow can require, via integrated checks:
- KYC Verification
- Identity Verification
- Security Confirmation
- Additional compliance checks
before a request is released for the operator to process.
4.3 Processing Time
Operators configure processing windows; the platform can flag approved requests for same-day handling.
Actual receipt times depend on:
- Blockchain network conditions
- Cryptocurrency selected
- Required network confirmations
4.4 Withdrawal Wallet Ownership
The integration validates that a destination wallet address is provided before a request proceeds.
Common causes of irreversible transfer errors, which the flow warns against, include:
- Incorrect wallet addresses
- Unsupported wallets
- Wrong blockchain networks
- User input errors
Transactions confirmed on the blockchain cannot be reversed.
5. KYC/AML Integration
The platform integrates identity-verification providers so operators can require verification before funding is enabled or withdrawals are released.
Documents an operator can require through the integration include:
- Government-issued Photo ID
- Proof of Address
- Selfie Verification
- Additional documents requested by the operator
Operators can restrict account functionality until verification is completed; the platform enforces the rules they set.
6. AML & Compliance Tooling
The platform provides AML and monitoring tooling operators can use to meet their own regulatory obligations.
The tooling can support operators who need to:
- Request proof of source of funds
- Request blockchain transaction evidence
- Delay transactions pending compliance review
- Reject suspicious transactions
- Freeze accounts involved in unlawful activity
- Report suspicious activity to relevant authorities where required
7. Third-Party Payments
The platform can enforce a rule that only the account holder funds and withdraws from their account, when the operator chooses.
When enabled, the registered account holder must be the beneficial owner of all funds moving through the account.
Any suspected third-party transaction can trigger:
- Transaction rejection
- Account suspension
- Compliance review
- Account closure
8. Withdrawal Restrictions
The platform lets operators decline or delay withdrawals in circumstances such as:
- Incomplete KYC verification
- Ongoing AML review
- Security concerns
- Suspected fraud
- Violation of the operator's terms
- Account disputes
- Technical issues beyond the operator's control
9. Internal Transfers
The platform can allow transfers between client accounts subject to the operator's approval workflow.
Additional verification can be required before approval.
10. Refund Handling
10.1 Refund Eligibility
Operators can configure a refund window — for example, allowing a refund request within 24 hours of a deposit where no trading activity has occurred.
10.2 Review Process
Refund requests can be routed for case-by-case review and may require identity verification.
10.3 Non-Refundable Situations
Operators can define situations where refunds are not offered, such as where:
- Trading activity has occurred
- Positions have been opened or closed
- Bonus abuse is suspected
- AML concerns exist
10.4 Refund Destination
The flow can return approved refunds to the original cryptocurrency wallet used for the deposit whenever technically possible.
11. Fees
The platform lets operators configure withdrawal fees, blockchain network fees, or processing fees where applicable.
Current fees are displayed within the client portal and are set by the operator.
12. Support and Escalation
Questions about the payment and wallet integrations can be submitted in writing to:
Email: [email protected]
Subject: Payment Integrations
We will route the enquiry to the JBM Market team responsible for the integration.
13. Risk Warning
Cryptocurrency transactions are irreversible and subject to blockchain network risks, volatility, and technical limitations.
Clients are responsible for verifying wallet addresses, network selections, and transaction details before submitting any transfer.
JBM Market provides the software and is not liable for losses resulting from client errors, blockchain failures, or third-party wallet service disruptions.
14. Updates
JBM Market may update the payment and wallet integrations described here at any time.
Any updates take effect when published on the JBM Market website.
Continued use of the JBM Market platform constitutes acceptance of the current integration set.
Read this alongside our Terms of Service and Privacy Policy.
See the integrations in action
Book a demo and see the payment and wallet integrations JBM Market can wire into your platform.