You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submitted a fix in #127 that supports both positional arguments initializePayment(onSuccess, onClose) and the object signature initializePayment({ config, onSuccess, onClose }), keeping backwards compatibility while preventing zero-argument crashes.
Activity
iamefe commentedon May 26, 2024
Same here.
kodervine commentedon Jun 19, 2024
I am having the same issue. Have you been able to work around this @multiman95 @iamefe
iamefe commentedon Jun 19, 2024
@kodervine Yes. Here's what worked for me:
I wrapped both onSuccess and onClose in curly brackets before they were recognized. I think the documentation needs to be updated.
kodervine commentedon Jun 19, 2024
That worked. Thank you so very much. Yes, definitely a documentation issue
iamefe commentedon Jun 19, 2024
You are welcome. I just made a pull request for the edit.
#106
kodervine commentedon Jun 19, 2024
Yeah hopefully. I know the older integration I'd had with paystack without the curly braces still work. But let's see what they resolve it
daviddivinefavour commentedon Jul 30, 2024
Well.. Thanks guys, was facing the same difficulty for over 40mins now
mylesodey commentedon Apr 23, 2025
You are a life saver, ive been stuck on this for days. Thank you
DevMubarak1 commentedon Oct 5, 2026
Submitted a fix in #127 that supports both positional arguments initializePayment(onSuccess, onClose) and the object signature initializePayment({ config, onSuccess, onClose }), keeping backwards compatibility while preventing zero-argument crashes.