Pay for Prime Pick.
Choose how you'd like to pay — your currency and billing period from the previous step will be confirmed on your invoice before anything is charged.
Select a payment method
Pay by Card
Processed securely via Flutterwave
Accepts Visa, Mastercard, Verve, and most local African bank cards — Flutterwave supports card payments across all currencies listed on the previous step.
Pay with PayPal
You'll be redirected to PayPal to confirm
Clicking below opens PayPal's secure checkout in a new step. You'll log into your PayPal account (or pay as a guest) and confirm the exact amount before anything is charged — nothing is charged on this page directly.
Pay with Crypto
USDT, BTC and ETH accepted
Send the exact equivalent of your plan's price to the wallet address below, then confirm your transaction hash. Your plan activates once the transaction is confirmed on-chain.
Pay by Bank Transfer
Local and international transfer supported
Transfer the exact amount shown on your invoice to the account below, using your reference code as the transfer narration so we can match it to your order.
Pay with Mobile Money
M-Pesa, MTN Mobile Money, Airtel Money and more
Available for Kenya, Uganda, Tanzania, Ghana and other supported markets — the right provider is matched automatically to the currency you selected on the previous step.
Nothing above is connected to a live payment processor yet — this is a design preview of the payment flow. Every method here will connect to a real processor (Flutterwave for cards and mobile money, PayPal directly, and a crypto/bank confirmation flow) once backend integration is complete.
Why there are five ways to pay, not just one
A single payment method is simpler to build, but it quietly excludes anyone whose everyday payment habits don't happen to match it — which, across the markets FDVS actually serves, would be a lot of people.
Card payments alone leave out a lot of people who'd otherwise want to subscribe — not everyone has a card that works internationally, and in several of the markets FDVS covers, mobile money is genuinely more common than card payments. Offering five methods instead of one is about meeting people where they already are, not adding options for their own sake. A subscriber in Lagos, one in Nairobi, and one in London are likely to reach for three completely different payment habits by default, and this page is built around that reality rather than assuming everyone pays the same way.
Card, via Flutterwave
Flutterwave handles card payments across every currency on the pricing page, including local African cards that international processors sometimes decline. It's the fastest method for anyone whose card already works internationally, and it's the default tab on this page since it covers the widest range of situations. Flutterwave specifically was chosen over a purely international-only processor because it's built to handle African card networks reliably, not as an afterthought bolted onto a system designed elsewhere first — that distinction matters more than it might seem for anyone who's had an international processor quietly decline a perfectly valid local card before.
PayPal
For anyone who already has a PayPal balance or prefers not to enter card details directly on a third-party site, PayPal handles the transaction on its own secure checkout. Nothing card-related is collected here — PayPal manages that entirely on its side, and FDVS never sees or stores the underlying card or bank details behind a PayPal payment, only the confirmation that it went through.
Crypto
Crypto payment is included specifically for markets where card and bank infrastructure can be unreliable or slow, and for anyone who simply prefers it. Confirmation depends on network speed rather than an instant processor response, which is the trade-off of paying on-chain versus through a card network — a payment can take anywhere from a couple of minutes to longer depending on network congestion, which is normal for on-chain transactions and not specific to FDVS's own processing. USDT is offered first since its value doesn't fluctuate the way BTC or ETH can between the moment you send and the moment it's confirmed.
Bank transfer
A direct bank transfer works well for larger amounts — a 1-year Pro subscription, for instance — where some people prefer a bank-to-bank transfer over entering card details for a bigger sum. It's also often the most familiar option regardless of market, and for anyone without a card at all, it can be the most straightforward way to pay without needing to set up anything new. The reference code shown on this page exists specifically so a transfer can be matched back to the right order even without any other identifying information attached to the transaction, which matters since bank transfers often arrive with minimal accompanying detail.
Mobile Money
M-Pesa, MTN Mobile Money, Airtel Money and similar services are how a significant share of everyday payments happen across Kenya, Uganda, Tanzania and Ghana specifically — offering it isn't an add-on so much as matching how people in those markets actually already pay for things online. The provider list on this tab is matched to the currency selected on the previous step, since a Kenyan Shilling payment and a Ghanaian Cedi payment naturally route through different mobile money networks, and asking someone to find a card just because that's the default elsewhere would be a genuinely worse experience than meeting them on the network they already use daily.
Nothing here is live yet
Every button on this page currently shows a plain preview message rather than actually charging anything — there's no real payment processor connected behind any of the five methods yet. That's stated plainly on the page itself rather than left to guesswork, the same honesty applied to every other placeholder feature across the site until the backend work behind it actually exists.
What happens once a real processor is connected
When Flutterwave, PayPal, and the crypto/bank confirmation flow are actually wired up, the interface on this page won't need to change — the tabs, the fields, and the layout are already built to match how each method genuinely works. What changes is purely behind the scenes: the "Pay securely with Flutterwave" button will call a real API instead of showing a preview alert, and a successful payment will actually activate the plan rather than just confirming the click landed. Building the front end first, honestly labeled as a preview, means the actual integration work later is a swap, not a redesign.