Enable cash and offline payment methods

Autofleet / locomotion

An open-source rider/passenger mobile app written in React Native and Node.js that can be customized and modified to support any ride-hailing

MIT License

33 stars 13 forks source link

Enable cash and offline payment methods #841

Closed joseuride closed 3 months ago

joseuride commented 3 months ago

Hi team,

I'm working on Cash and Offline payment methods. But I can't enable these options on Control Panel. Can you share with me how to enable them for AF Service?

Screenshot 2024-08-13 at 13 38 07

michalbanin commented 3 months ago

We will add this for you and let you know once we're done

michalbanin commented 3 months ago

Hi @joseuride , we've added the cash and offline options to the service in the staging env.

joseuride commented 3 months ago

Thanks @michalbanin. I will check it

tonyuride commented 3 months ago

Hi @michalbanin , I checked the payment cash and offline mode but it's still disabled in control panel.

Screenshot 2024-08-16 at 15 44 46

michalbanin commented 3 months ago

Hi @tonyuride I'm able to see all options, which client are you selecting?

tonyuride commented 3 months ago

@michalbanin Can you set up a ride completely (choose the address to pick up and drop off)? Then select the payment method and you will see it's disabled.

michalbanin commented 3 months ago

Hi @tonyuride, the reason it wasn't working is because the pricing policy you created was set to the "Uride Thunderbay" demand source, and not "Uride Rider", which is the app demand source which the service is connected to. It should be working now

6ewis commented 3 months ago

@michalbanin you set Uride thunder bay "We set one service, "Thunder Bay car," and one pricing policy for your testing. Thunder Bay's territory is defined"

Can you please send invite for "Uride rider" too ?

michalbanin commented 3 months ago

@6ewis I think there is a confusion here, let me clarify: There are 2 demand sources in your env:

Uride rider (ID c625ee1e-4a13-49ac-b5a8-8d121965c294)- which is the demand source we created for you when we granted you access in July 2024 specifically for the forking process. Services are connected to this demand source, and the pricing policy we created was connected to it as well.
Uride Thunderbay (ID d333f31d-bd55-4c8b-87b0-b6d15c52eecf) - was set up when the env was created during the Uride implementation process, 2 years ago.

It seems that the app you're building is based on the Uride Thunderbay demand source. We have two options:

We will connect the services and pricing to the Uride Thunderbay demand source
You can change the app demand source to Uride rider

Let me know which you prefer

michalbanin commented 3 months ago

@6ewis Updating that we've connected the services to "Uride Thunderbay" demand source. The demand source is connected to your stripe account.