n the new system, if a credit card is stored at the user's profile level, the user can use that card to book rides using that card if he or she is the end traveler. The user can can also book rides for others using the credit card stored at their profile level, but they will have to manually type in the traveler's information and forward on the confirmation emails.
However, if a user is acting as a delegate and booking on behalf of someone else, he/she will go to the profile and add themselves as a delegate/booker for the person they need to book travel for. After becoming a delegate for someone, they user will click the "Start Assisting" button and click the Account icon where they can view whether that user has a credit card stored in their profile. If the user does have a credit card entered at the profile level, the delegate will see it as a selectable card under the payment options dropdown menu. If the user doesn't have a card, the delegate can enter a card for them at the profile level and then go back to the purchase page and the card will appear as selectable. Once the card is entered for this user at the profile level, the delegate will not have to add payment cards in the future unless they want to change the user's credit card.
Users also have the option of entering a credit card during the booking flow but it will not be saved at the user's profile level.
In the old system, users could store credit cards for other individuals and use them to book a ride for the traveler. This differs from the new system which requires that a credit card be tied to the end traveler's profile in the application.
See the section to the left about the steps a user needs to take to attach a credit card to the end traveler's profile so that he or she can complete the transaction as the delegate of the end traveler.
