SwapBee × BlockBee: Automated Crypto Payment Conversion
BlockBee and SwapBee connect cryptocurrency payment collection with post-payment conversion. BlockBee detects incoming funds and applies the merchant’s exchange automation rules. When a rule uses SwapBee, SwapBee compares available conversion routes, and the resulting asset is forwarded to the merchant’s configured destination address. Conversion is best effort and remains subject to asset, network, amount, and provider availability.
What the BlockBee and SwapBee integration does
BlockBee provides the payment infrastructure: it receives or orchestrates the cryptocurrency payment, detects it on-chain, and applies the account’s saved automation rules. In the BlockBee dashboard, a user enables SwapBee and defines a “From Coin” and “To Coin” rule, with higher rules taking priority.
When an eligible payment matches a configured rule, BlockBee’s automation invokes SwapBee as the exchange provider. SwapBee handles the routing layer by obtaining and comparing available routes from its providers. The chosen route performs the conversion, and the output is sent to the destination address configured for the selected asset and network.
The official BlockBee documentation describes these conversions as best effort. If no quote is available when the payment is processed, BlockBee forwards the funds in the original asset to the configured address instead of guaranteeing a conversion.
How automated crypto payment conversion works
- A customer pays an invoice in BTC through BlockBee.
- BlockBee detects the payment and waits for the required blockchain confirmation state.
- The merchant’s saved automation rule requests settlement in USDT on the network associated with the configured USDT destination.
- SwapBee obtains available BTC-to-USDT conversion routes from supported providers.
- Route execution follows the available SwapBee quote and the BlockBee automation rule. Public documentation confirms that SwapBee provides the routing layer, but does not separately document an operator-controlled route-selection step inside this automated flow.
- If a suitable route is available and the conversion completes, USDT is delivered to the merchant’s configured address. If no quote is available at processing time, BlockBee’s documented fallback is to forward the original BTC.
Example: converting BTC payments to USDT
A merchant may accept BTC from customers but prefer to hold USDT. Converting after payment can reduce ongoing BTC price exposure, simplify treasury operations, consolidate receipts into one settlement asset, and deliver funds on a network that fits the merchant’s wallet and accounting setup.
The merchant enables SwapBee in BlockBee, adds a BTC-to-USDT automation rule, and configures a compatible USDT destination address for the intended network. Once a confirmed BTC payment qualifies for the rule, the integration requests an available conversion route.
The final USDT amount is not fixed in advance. It can vary with the live quote, provider and network fees, market movement, and processing conditions. Route availability, processing time, and any compliance requirements can also vary by provider, amount, destination, and jurisdiction.
Benefits for businesses
- Automated post-payment conversion: eligible incoming payments can be converted according to saved rules rather than handled one by one.
- Less manual treasury work: teams do not need to move every receipt to an exchange and place a separate trade.
- Configurable settlement assets: merchants choose supported From Coin and To Coin combinations and can prioritize multiple rules.
- Access to multiple available routes: SwapBee compares routes from supported providers instead of relying on a single fixed exchange path.
- Direct delivery: BlockBee describes its payment infrastructure as non-custodial, forwarding funds to configured wallets; SwapBee routes conversions to the selected provider and destination rather than presenting itself as the merchant’s custodial account.
- A clearer payment-to-settlement workflow: collection, conversion rules, and destination configuration are connected in one operational process.
Fees, rates and processing times
Quotes depend on the providers available for the requested pair and on current market conditions. Provider and blockchain network fees may apply, so the displayed quote should be reviewed before execution where the workflow provides that opportunity. An automated rule should not be treated as a promise of a fixed rate or fixed final amount.
Blockchain confirmation times and provider processing times vary. Network congestion can delay payment detection, conversion, or settlement. A competitive available quote at one moment may change before a later payment is processed.
Compliance and availability
Availability can depend on the incoming asset, requested settlement asset, network, amount, destination address, jurisdiction, and provider. Providers may apply compliance or risk checks. Using a flow that does not require a SwapBee account should not be interpreted as guaranteed no KYC in every case.
The destination address must be compatible with the selected asset and network. Sending to an address on the wrong network can result in lost funds. Merchants should also check minimum transaction requirements and the supported To Coin options shown for the selected From Coin.
Who this integration is for
The integration is relevant to merchants that accept several cryptocurrencies but want settlement in one treasury asset; platforms that want to reduce manual handling after crypto payments; businesses automating payment and treasury operations; and products already using BlockBee payment infrastructure that need configurable conversion rules.
It is not a guarantee that every payment pair, network, amount, or destination can be converted. Each workflow should account for the documented fallback to the original asset when no quote is available.
Getting started
Review BlockBee’s official SwapBee automation guide to enable the provider, create From Coin and To Coin rules, set their priority, and save the configuration. Confirm that the appropriate destination addresses are configured in BlockBee before enabling live payment flows.
To understand the routing side, visit SwapBee and read how the crypto swap aggregator compares available provider quotes. Merchants evaluating the example in this article can also review the BTC-to-USDT conversion page and consult the SwapBee Help Center for current product guidance.
Start by configuring a supported destination address and one test automation rule in BlockBee, then verify the complete payment-to-settlement flow with an amount above the applicable minimum before using it in production.