Merchant does not support Rave v3

[5ran6]

For some reason, Merchant does not support Rave v3 still affects the library. Is there any way to bypass this so I can use v2? Thanks

[nelsonweze]

Hi, it's showing that because Flutterwave requires Merchants to submit their PCS DSS certificates before they are enabled to use v3 which is the default version of the package at the moment.
What I can do is make the package to support v2 so you can choose which version you want.

[5ran6]

This will be perfect. How long do you think it will take for the new update?

[nelsonweze]

Already on it. Before the end of today hopefully

[nelsonweze]

@5ran6 I have pushed version 1.0.2 to fix the issue. Confirm please

[5ran6]

Alright. Lemme do that now

…

On Mon, May 31, 2021, 15:01 Nelson Eze ***@***.***> wrote: @5ran6 <https://github.com/5ran6> I have pushed version 1.0.2 to fix the issue. Confirm please — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEACWBZN5ONBP2F6BHM25ITTQOJCNANCNFSM452L2EDQ> .

[5ran6]

Well done. I updated my plugin to 1.0.2 and Added the Version param in the PayInitializer but still the same result. Take a look at the attachment. So what is next?

On Mon, May 31, 2021 at 3:01 PM Francis Ocholi ***@***.***> wrote: Alright. Lemme do that now On Mon, May 31, 2021, 15:01 Nelson Eze ***@***.***> wrote: > @5ran6 <https://github.com/5ran6> I have pushed version 1.0.2 to fix the > issue. Confirm please > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEACWBZN5ONBP2F6BHM25ITTQOJCNANCNFSM452L2EDQ> > . >

<img width="1435" alt="Screenshot 2021-06-01 at 03 56 34" src="https://user-images.githubusercontent.com/16788231/120263880-822f0500-c294-11eb-8452-e8eb3febc02c.png">

[nelsonweze]

Could you try adding it instead in the setup function where you initialise your keys? But I will however check for this case.

[5ran6]

Ok, I will do that.

…

On Tue, Jun 1, 2021, 13:33 Nelson Eze ***@***.***> wrote: Could you try adding it instead in the setup function where you initialise your keys? But I will however check for this case. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEACWB5MQXDTSGD2Q3FEJP3TQTHQXANCNFSM452L2EDQ> .

[nelsonweze]

Is it working now @5ran6 ?

[5ran6]

Sorry for the delay in reply. Moving forward, I will give you prompt responses. So From the screenshot, you will see it didn't still work after doing it in the main function. Did you try it and it worked?

[Mytripnigeria]

@nelstein any help/fix to this?

[nelsonweze]

Let me test again from my end and share a screenshot.

[Mytripnigeria]

Let me test again from my end and share a screenshot.

Okay, anything yet?

[nelsonweze]

It works from my end actually. Are you using a test card or actual card?
I just pushed a commit that makes the setup function the only place to initialize keys, staging and version.
You can try accessing directly from github and let me see if it makes any difference.

[nelsonweze]

Still encountering this issue @5ran6 ?

[Mytripnigeria]

@nelstein fixed. Thanks for the support. Any plan on ussd & bank transfer in the future?

[5ran6]

Yes, it is working. Sorry I wasn't feeling well so I didn't test in time. USSD and transfer will make the package the ultimate one. What do you think?

…

On Thu, Jun 10, 2021 at 5:12 PM Mytripnigeria ***@***.***> wrote: @nelstein <https://github.com/nelstein> fixed. Thanks for the support. Any plan on ussd & bank transfer in the future? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEACWB6GQ5DHAT4D24KVYZ3TSDP5FANCNFSM452L2EDQ> .

[nelsonweze]

Okay great! I will look into that. Meanwhile I am going to close this issue. You can open another one to track the feature request.

[5ran6]

Okay great! I will look into that. Meanwhile I am going to close this issue. You can open another one to track the feature request.

Alright. Thanks. Also please finalize your "Save Card" feature. You are doing well! ✌️

[nelsonweze]

The intended behaviour works. If the transaction was successful and the user opted to save card, the onComplete function returns a card object. You can save this to your database. To charge from a saved card, you need to fetch the list of saved card objects from your db and use the function from the example codes.

[5ran6]

Ait. Just wanted to be sure card object returned was valid. Nice. Why about the other functions like bank transfer and USSD?

…

On Sat, Jun 12, 2021, 20:59 Nelson Eze ***@***.***> wrote: The intended behaviour works. If the transaction was successful and the user opted to save card, the onComplete function returns a card object. You can save this to your database. To charge from a saved card, you need to fetch the list of saved card objects from your db and use the function from the example codes. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEACWBYUJGOJMWOLKIDK7MLTSO4CRANCNFSM452L2EDQ> .