Connect it
Flutterwave is a tile under Configurations → Integrations → Payments. There’s no “sign in with Flutterwave” button: you copy one key out of your Flutterwave dashboard, make up one value of your own, and paste both in.1
Copy your secret key
In your Flutterwave dashboard, open Settings → API Keys and copy your secret key. It starts
with
FLWSECK. The public key (FLWPUBK) sits right beside it and is not the one DMLY needs;
paste it by mistake and the tile tells you so.There is no environment dropdown in DMLY. The key decides whether you are taking real money:
FLWSECK_TEST-… is test mode and FLWSECK-… is live. Check it before you paste.2
Choose a secret hash
Flutterwave does not hand you a webhook secret; you invent one. Make up a long random value (a
password manager’s generator is ideal) and type it into the tile’s Secret hash field. You will
type the same value into Flutterwave in a moment.
3
Connect
Paste the secret key into its field and click Connect. DMLY checks the key with Flutterwave
straight away, so a typo fails now rather than at the first real payment. The webhook URL appears on
the tile once you’re connected.
4
Add the webhook in Flutterwave
DMLY does not register the webhook for you. In Flutterwave, go to Settings → Webhooks, paste the
URL from the tile, enter the same secret hash you typed into DMLY, tick every box (webhook
retries included) and save.Test mode and live mode each have their own webhook settings in the Flutterwave dashboard. Set the
URL and secret hash in the mode your key belongs to.
5
Take one real payment end to end
Send yourself a small invoice, pay it, and confirm it flips to Paid on its own. If it doesn’t,
the webhook isn’t reaching DMLY; fix that before a client pays.
How DMLY confirms a payment
A Flutterwave webhook is treated as a hint, not proof. When one says a payment completed, DMLY asks Flutterwave’s own verification service about that transaction and uses only what Flutterwave confirms: the status, the amount, the currency and the reference. A message that claims more than Flutterwave will confirm changes nothing.The client paid less than asked, or in another currency
The client paid less than asked, or in another currency
DMLY does not mark the payment as paid. A booking isn’t confirmed and the client isn’t sent a
receipt. Your team gets a Paid amount differs from the bill alert, and the details are in
Reports → Logs. Talk to the client, then either record the payment yourself under
Finance → Payments or refund it.
The client paid more than asked
The client paid more than asked
The payment is marked paid at the amount you billed, and your team gets the same alert, because the
client is owed the difference.
A card was declined
A card was declined
Nothing changes on the payment. Flutterwave’s page lets the client try again on the same link, so a
declined attempt is not treated as the end of the checkout. A pay-before booking hold simply runs to
its normal length.
Card or bank transfer
A Flutterwave pay link offers every method your account has switched on for the link’s currency. In a payment step, set Payment method to Bank transfer only and the checkout opens on a one-time account number, as it does on Paystack. Card only restricts it to card. A bank-transfer link holds a pay-before booking for the longer transfer time (see Appointment payments).Flutterwave only honours that restriction while Disable preferred payment methods is off in your
Flutterwave business preferences. If it’s on, the link opens on every method whatever the step says.
Refunds
The Refund button refunds through Flutterwave, in full or in part, for any payment method. The money comes out of your Flutterwave balance, and the smallest refund Flutterwave accepts is NGN 100 (KES 10 in Kenya). If Flutterwave refuses the refund request, nothing changes in DMLY and you see Flutterwave’s reason. If it accepts the request, DMLY marks the payment Refunded straight away, while Flutterwave finishes the refund in the background: card refunds can take 3 to 15 days to reach the client, bank refunds about a day. To have refunds you make in the Flutterwave dashboard show up in DMLY too, switch on Flutterwave’s refund webhook with the same URL. Should Flutterwave report that a refund failed, your team gets a Refund failed alert and the reason is in Reports → Logs.Current limitations
These are known behaviours of the Flutterwave integration today, not faults to report.Subscriptions can't auto-charge a saved card yet
Subscriptions can't auto-charge a saved card yet
DMLY doesn’t save Flutterwave cards for automatic renewals yet. A subscription on Flutterwave is
collected with a pay link each cycle. Use another gateway for automatic renewals (see
Subscriptions).
No account number in the chat
No account number in the chat
Account number in chat (automatic) is a Monnify feature. On Flutterwave, Bank transfer only
puts the account number behind the link instead.
A currency your account can't take fails when the link is made
A currency your account can't take fails when the link is made
DMLY passes the currency straight to Flutterwave, so a pay link in a currency your Flutterwave account
hasn’t enabled fails when it is made, with Flutterwave’s reason.
Payments and gateways
Pay links, payment statuses and what a failed webhook means.
Collect bank transfers in chat
Transfer-only links, your own account details, and letting the client choose.

