-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop.rental_methods vs. fare_attributes.payment_type #844
Comments
Stops may be a bit of an outlier right now and should just stay aligned with GBFS and reference that externally. For the modes, I think 1) paratransit needs to be removed from delivery robots, 2) credit_card added to delivery robots. applepay vs androidpay is too specific a field for us in MDS land I think. But What are the values for micromobility? |
The
Roger 👍 In openmobilityfoundation/mds-openapi#5 I updated the casing to match exactly with GBFS.
Done in openmobilityfoundation/mds-openapi#5
Happy to do this as well. |
@schnuerle in thinking about adding |
Phone is when a reservation is made via a phone call, to a phone number. So it's different from a mobile app. |
Payment types are aligned in this commit. Ready to close this issue when confirmed by @thekaveman. |
Looks good 👍 |
Issue
Stops defines the
rental_methods
field as follows:GBFS Rental Methods
as of April 2023 are:key
creditcard
paypass
applepay
androidpay
transitcard
accountnumber
phone
Further, some modes support the
fare_attributes.payment_type
field, with a different list of options and the the following variation:care-share
delivery-robots
passenger-services
cash
credit_card
mobile
voucher
paratransit
no payment
test
The text was updated successfully, but these errors were encountered: