STP Bitcoin Settlement Mechanics: How $90K Actually Moves From Your Wallet to the Fundo Nacional de Transformação

Moving $90,000 from a self-custody wallet into São Tomé & Príncipe’s National Transformation Fund (FNT) is rarely walked through paragraph by paragraph. This article preserves the workflow 21 CBI documented when STP was a productized offering. It is historical analysis, not a current payment instruction or custody promise. 21 CBI no longer productizes STP; a current bespoke engagement must re-verify the receiving parties, settlement rail, custody terms, and government instructions before funds move.

Then the same Bitcoiners commit the equivalent of $90,000 in Bitcoin to a sovereign donation fund and treat the settlement leg as a black box. "I’ll send Bitcoin, they’ll handle it, the passport shows up." The documentation on the public side describes the program, the fund, and the timeline. The actual mechanics by which Bitcoin moves from the applicant’s wallet to the Fundo Nacional de Transformação’s account in São Tomé is the part that does not appear in marketing material.

It is the part this article is about.

The $90,000 single-applicant contribution to São Tomé & Príncipe’s Citizenship by Investment (CBI) program, codified under Decreto-Lei n.º 07/2025, is the lowest-priced sovereign donation in the citizenship-by-investment market. The UCID in Dubai screens the application, a 90-day window opens upon approval-in-principle, and the contribution is then deposited into the Fundo Nacional de Transformação (FNT). Under the former product model, 21 CBI received the Bitcoin, converted it, and instructed the wire. The sections below document that former workflow.

The Three-party Architecture

Three entities sit on the path between your wallet and the FNT.

01 / The applicant. You hold the BTC. You sign the transaction or authorize the Lightning payment. The provenance trail going back to acquisition is yours, and it gets documented separately from the payment leg.

02 / The former 21 CBI role. Under the productized workflow, Bitcitizen LLC operating as 21 CBI received the Bitcoin into a segregated address, held it temporarily for conversion and onward transfer, converted to USD, and instructed the wire to the receiving bank. Where a file required it, the firm made the payment to the UCID on the client’s behalf. None of those operational steps should be assumed for a current bespoke engagement.

03 / The receiving bank. Final settlement to the FNT runs through the receiving bank. The bank credits the fund’s account, posts the receipt to the file, and the UCID clears the citizenship-grant step.

The documented architecture was intentionally short. There was no third-party VASP layered between the applicant and 21 CBI. BTC moved to a firm-controlled address, not directly to a sovereign government wallet, and the temporary-custody window lasted only through conversion and wire. Current custody and conversion terms must be stated in a bespoke engagement letter before any transfer.

The On-chain Leg

For most files, the on-chain leg runs over Bitcoin mainnet. Lightning is operationally usable but rarely the right tool for a $90,000 transfer, where outbound channel capacity is the binding constraint for clients who do not run a node sized for liquidity at that scale.

The mechanics:

01 / Address generation. The former workflow issued one deposit address per file, segregated from any other client’s funds, with a signed message proving control. Any current address, proof-of-control method, and receiving entity must be verified from fresh written instructions before broadcast.

02 / Test transactions. The documented workflow used small test transactions before the main transfer to confirm address parsing, network connectivity, and confirmation flow. The tests were operational hygiene, not theater. They caught address-substitution and wallet-firmware issues before the main transfer confirmed on-chain.

03 / The main transfer. The full contribution-equivalent BTC was sent with fee priority set to confirm inside one to three blocks and replace-by-fee enabled. The transaction was broadcast from the applicant’s wallet; 21 CBI did not co-sign.

04 / Confirmation threshold. The former workflow waited for five confirmations before the conversion leg began. The off-chain leg did not start on zero-conf or single-confirmation receipts. A current bespoke scope must state its own confirmation policy.

For Bitcoiners with multisig custody, the signing ceremony runs the same way it would for any other large outbound transfer: each signer reviews the unsigned transaction, signs in turn, and the broadcast happens after the threshold is met. PSBTs are the standard format. The former workflow did not require access to the applicant’s seed, hardware wallets, or signing flow; only the final transaction appeared on-chain.

Lightning can be an option where BTC sits in a node with sufficient outbound capacity. For most applicants, opening or rebalancing a $90,000 channel for a one-time payment is more operational friction than a single mainnet transaction. Whether Lightning is available for a current bespoke file must be confirmed in the written payment scope.

The Off-chain Leg

Once the on-chain transaction reaches the five-confirmation threshold, the off-chain settlement starts.

01 / Conversion to USD. The former workflow converted at the prevailing market rate on the day of transfer, without a lock-at-quote or a proprietary pricing convention. The conversion-day spot rate produced the operative USD figure for the program.

02 / USD wire to the receiving bank. Under that workflow, fiat moved from 21 CBI to the receiving bank handling final settlement to the FNT. The bank booked the credit to the fund’s account on the file reference and notified the UCID.

03 / FNT acknowledgement and citizenship issuance. The UCID records the contribution as satisfied and clears the citizenship-grant step. The decreto-lei grants citizenship on receipt of the contribution; passport issuance follows the standard biometric and document workflow.

The pricing convention deserves a separate paragraph because it is the question Bitcoiners ask first. Under the documented workflow, the price was the prevailing market rate on the day of transfer. Client BTC was not warehoused in a treasury position waiting for a more favorable spot. Conversion ran when the on-chain transaction reached the confirmation threshold. Price risk sat with the applicant between approval-in-principle and the chosen broadcast date inside the 90-day window.

The Confirmation Number

The artifact that gated the post-payment workflow was a single confirmation number issued by the receiving bank: the transfer reference confirming that fiat had landed at the bank designated to settle to the FNT, against the applicant’s file. The former workflow delivered that number to the client when the bank issued it.

The number is the artifact the file references in any future administrative review. It anchors the contribution to the applicant, ties it to the file, and is what the UCID posts against the citizenship-grant step. Under the former workflow, 21 CBI retained a copy alongside the file while the original record belonged to the client.

This also answers what followed an on-chain confirmation. The transaction ID evidenced that BTC left the applicant’s wallet. The bank-issued confirmation number evidenced that the contribution settled to the fund. Two artifacts, two distinct purposes, both retained against the file.

Source Of Funds Vs. Payment Mechanics

The two are separate workstreams and should be kept separate in your head.

The payment mechanics describe how the BTC moves. The source-of-funds package describes where the BTC came from. The UCID’s diligence on the source-of-funds file runs in parallel with the application review; the payment mechanics run after approval-in-principle. A Bitcoiner with a clean exchange-and-self-custody trail clears source of funds on the same statutory standard as a Bitcoiner whose stack came from mining revenue or from a Wyoming LLC operating in the Bitcoin economy. The artifacts differ; the standard does not.

The documented payment mechanics were deterministic. Once approval-in-principle issued, the 90-day window opened and the settlement architecture followed the same playbook regardless of where the sats came from. The on-chain leg, conversion, wire, and confirmation number used one sequence.

Refund Posture And Denial Cases

The applicant does not deposit funds into the FNT on a hope. Decreto-Lei n.º 07/2025 sequences approval before contribution: the UCID issues approval-in-principle, the 90-day window opens, and only then does the BTC leave the applicant’s wallet. If a file is denied at the diligence stage, no contribution is made; the BTC never leaves your custody.

Under the former workflow, if a downstream operational issue surfaced after broadcast but before the receiving bank settled to the FNT, the position remained under 21 CBI’s control until resolution. BTC, or converted USD if the issue surfaced post-conversion, was held against the file reference and reconciled back to the applicant. Funds were not co-mingled with other files.

The Principle

The cheapest CBI on Earth ran through plumbing the marketing material did not describe. Under the former 21 CBI model, the equivalent of $90,000 in Bitcoin left the applicant’s wallet, entered temporary custody, converted to USD at the prevailing market rate, and moved through a receiving bank to a Ministry-of-Finance-administered fund. The bank issued a confirmation number as the settlement evidence. A current bespoke engagement may use different parties or rails and must document them before transfer.

Bitcoiners verify before they trust. The preserved architecture made each leg verifiable: a signed message proving address control before broadcast, on-chain confirmations against the transaction ID, and a bank-issued confirmation number against the file. Those remain sensible controls for any sovereign Bitcoin payment, but they are not a current promise about an STP engagement.

Programs change. The programs available today may not exist next year. Every CBI threshold increase in history has been upward. Low time preference does not mean no action. It means making the right move at the right time.

If you want to determine whether STP belongs in your architecture and what a current settlement path would require, start with the paid Sovereignty Strategy Session. No obligation to proceed beyond the session.

Adam Juchniewicz, CEO US Air Force veteran. Bitcoiner since 2020. Licensed agent of The Bitcoin Office of El Salvador.