Skip to content

Paystack SDK fails to load non-card channels when card is excluded [BUG]  #14

Description

@John-Daniels

Paystack SDK fails to load non-card channels when card is excluded

🐛 Bug Description

The payment process fails with the error message "card payments are not supported. please reach out to your merchant for further information" when a transaction is launched with an access_code initialized for non-card channels like bank_transfer, bank, or ussd.

The transaction initialization succeeds and works correctly when the required channel is card. The error only occurs when the Paystack UI is launched for payment methods other than card.

Image

When i use payment channel card

Image

🔄 To Reproduce

Steps to reproduce the behavior:

  1. Server-Side: Initialize a transaction using the Paystack API, ensuring the channels array in the request includes only non-card options (e.g., ["bank_transfer", "bank", "ussd"]) and does not include "card".
  2. Server-Side: Obtain the resulting access_code.
  3. Flutter App: Call the launch() method of the PaystackPlugin using the access_code from step 2.
  4. See Error: The Paystack UI displays a critical error immediately upon launch or when trying to load the payment options: "card payments are not supported. please reach out to your merchant for further information".

✅ Expected Behavior

When the access_code is initialized for non-card payment channels (bank_transfer, bank, ussd), the Paystack UI should load the available payment options (excluding card) and allow the user to complete the transaction successfully.

📱 Smartphone (Example)

  • Device: [e.g. iPhone 16]
  • OS: [e.g. iOS 17.5]
  • Paystack Flutter SDK Version: [^0.0.1-alpha.2]

➕ Additional Context

  • The server-side transaction initialization is confirmed to be successful and returns a valid access_code.
  • When the server-side initialization includes the "card" channel, the payment flow works correctly.
  • The issue is that the SDK appears to check for card support regardless of the configured channels, and if the card channel is not available (either due to account setting or deliberate channel exclusion), it throws this misleading error, blocking all other payment methods.
  • The merchant account on the Paystack dashboard has bank_transfer and ussd enabled.

Activity

  1. changed the title [-][BUG][/-] [+]Paystack SDK fails to load non-card channels when card is excluded [BUG] [/+] on Oct 10, 2025
  2. added
    enhancementNew feature or request
    and removed
    bugSomething isn't working
    on Oct 10, 2025
  3. damilola-paystack commented on Oct 10, 2025

    @damilola-paystack
    Member

    Hey @John-Daniels this is actually not a bug. We currently don't support those channels on the SDK. But I realised we didn't highlight supported channels in any of the documentation. If you don't mind, please fill this form so it can help us prioritise the channels to work on.

  4. John-Daniels commented on Oct 10, 2025

    @John-Daniels
    Author

    Alright @damilola-paystack Thanks for the swift feedback I will love to collaborate on this, I dropped a comment on the theming system issue in my feedback.

    I'm looking forward to the other payment channels. Thanks.

  5. git-temak commented on Jan 28, 2026

    @git-temak

    Hi @damilola-paystack please do you have any updates with this yet or estimated timelines when additional payment channels would be available? I also ran into some issues with this and have filled the linked form. One thing to note, the form asks for email multiple times

    Image

    It would be really handy to have some sort of documentation on what works with the package. At the moment, when initialising payment, only 'card' option shows the payment sheet in the app (when nothing is passed, I get the error 'There are currently no payment channels on your integration that are supported by the SDK').

    Also when the device uses dark mode, the payment sheet is not visible. I'm not sure if this is the theming issue that @John-Daniels also ran into. Happy to open a separate issue for that if preferred

    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions