Appearance
Configuration reference
For merchants
Where: Extensions → My extensions → Flutterwave → ⋯ → Configure Stored as: KommandhubFlutterwaveSW.config.<key>Scope: every setting can be set per sales channel. Use the sales-channel selector at the top of the configuration screen; a field left untouched inherits the All Sales Channels value.
Live configuration
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Public Key | apiPublicKey | Password | — | Live public key, FLWPUBK-…. |
| Secret Key | apiSecretKey | Password | — | Live secret key, FLWSECK-…. Used for all API calls in live mode. |
| Webhook Secret Hash | secretHash | Password | — | The live secret hash you set under Settings → Webhooks in the Flutterwave dashboard. A value you choose, not an API key. Webhooks are rejected until it is set. |
Test configuration
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Enable Sandbox | enableSandbox | Toggle | Off | Use the test keys and test hash below instead of the live ones. |
| Public Key | apiPublicKeySandbox | Password | — | Test public key, FLWPUBK_TEST-…. |
| Secret Key | apiSecretKeySandbox | Password | — | Test secret key, FLWSECK_TEST-…. |
| Webhook Secret Hash | secretHashSandbox | Password | — | The test-mode secret hash. Flutterwave allows a different hash for test and live. |
Webhooks are verified with the secret hash of the active mode as saved on All Sales Channels; per-sales-channel hashes are not used for webhooks.
Required: the secret key for the active mode (checkout is blocked with a configuration error otherwise), and the webhook hash for the active mode (webhooks are rejected otherwise).
Customization
Shown on Flutterwave's hosted payment page, not in the Shopware checkout. To change how the method appears in your checkout, edit the payment method under Settings → Shop → Payment methods.
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Title | title | Text | Pay with Flutterwave | Title on the Flutterwave page. |
| Description | description | Text area | — | Short text on the Flutterwave page. When empty, Flutterwave shows Developed with ❤️ by Kommandhub. |
| Payment Method Logo | logo | Media | — | Intended as the logo on the Flutterwave page. Currently the media ID is sent where Flutterwave expects an image URL, so the logo is unlikely to appear. See Known issues. |
| Payment Options | paymentOptions | Multi-select | all | No effect in 0.9.0-beta.1 — the selection is saved but not sent to Flutterwave. The options offered follow your Flutterwave account. |
Configuration
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Session Duration (minutes) | sessionDuration | Integer | 30 | No effect in 0.9.0-beta.1. |
General
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Max Retry Attempts | maxRetryAttempt | Integer | 3 | No effect in 0.9.0-beta.1. |
Refunds
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Enable Refunds | refundEnabled | Toggle | On | Allow refunds from the order's Flutterwave tab. |
| Minimum Refund Amount | minimumRefundAmount | Decimal | — | Smallest refund, in the order currency's main unit (100 = ₦100). Empty: the plugin's built-in minimum — NGN 100, KES 10, no minimum for other currencies. |
Bank data collection
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Enable Bank Data Collection | collectBankData | Toggle | Off | Show a bank-account form in the customer account. |
| Bank Country (ISO code) | bankCountry | Text | NG | Two-letter country whose bank list is offered — e.g. NG, GH, KE, UG, ZA, TZ. |
| Show BVN Field | showBvnField | Toggle | Off | Add a BVN field. |
| Require BVN | requireBvn | Toggle | Off | Make the BVN mandatory. |
Debugging
| Setting | Key | Type | Default | Description |
|---|---|---|---|---|
| Enable Detailed Logging | enableDebugging | Toggle | Off | Log detailed payment events. Errors are always logged. |
| Log levels to log | logLevels | Multi-select | all | Restrict detailed logging to these levels. |
Flutterwave logs go to Shopware's main log file with the prefix [Flutterwave]. See Troubleshooting → Logs.