Skip to main content

Confirm Request


Use the Confirm Request screen to review request details and submit the appointment request.

This screen includes

  • Doctor summary header with doctor name, specialty, and profile image.
  • Request summary section that displays the selected appointment date, time, and clinic location, with a note that shows when the exact location becomes available after confirmation.
  • Appointment fee section that displays the fee in the doctor’s currency and an estimated amount in the user’s currency.
  • Payment method selector with options for Apple Pay, Google Pay, and credit card.
  • Credit card form with a required card number field.
  • Save payment details option that allows secure storage of card details for future bookings.
  • Security notice that indicates secure payment handling and supported card types.
  • Billing and charge notes that explain charge timing, possible additional fees, currency rules, and cancellation limits.
  • Doctor availability fallback option that allows assignment to another available doctor when the selected doctor becomes unavailable.
  • Terms and privacy consent checkbox that requires agreement to the Terms of Use and Privacy Policy and consent for health data processing.
  • Primary action button that confirms the request and submits the payment authorization.

Workflow

This screen appears after the user selects an appointment location and time.

  1. Choose a payment method and provide the required payment details.
  2. Review the appointment fee, currency information, and billing notes.
  3. Enable the option to save payment details, if needed.
  4. Review the security notice and supported payment methods.
  5. Agree to the Terms of Use and Privacy Policy by selecting the required consent checkboxes.
  6. Select Confirm Request to submit the payment authorization and continue.
notes
  • The app monitors request validity and provider availability.
  • If provider availability changes before submission, the app applies the configured fallback rules.
  • If the request expires before submission, the system sets the request state to expired.
  • After submission, the app persists the request and prevents further edits.

Validations

These rules control payment visibility, input requirements, and submission eligibility.

ScenarioApp BehaviorSDK Output
Payment is not required.Hides the payment section and allows submission.Returns a request state without payment authorization.
Payment is required.Displays supported payment methods for the platform.Returns a request state that requires payment authorization.
Payment options load.Preselects a payment method based on default logic.Returns the proposed payment method.
A saved card exists and was previously stored.Selects the saved card by default.Returns the saved card reference.
No saved card is available.Selects the first available payment method.Returns the default payment method.
A wallet-based method is selected.Hides manual card input fields.Indicates wallet-based payment selection.
A card-based method is selected.Requires valid card details.Returns validation errors for invalid or missing input.
Submission occurs with invalid payment details.Blocks submission and highlights errors.Returns a payment validation error.
Payment authorization fails.Blocks submission and remains on the screen.Returns a payment authorization error.
The request expires before submission.Disables submission and editing.Returns a request state of expired.

Actions

These actions describe how the request completes or exits.

ScenarioApp BehaviorSDK Output
Review of the request occurs.Displays appointment and payment summary details.Returns the current request state.
A payment method change occurs.Updates the selected method on the screen.Returns the updated payment method.
Entry of new card details occurs.Validates input and enables submission.Returns validated card details or errors.
Submission occurs with a card-based method.Processes payment and submits the request.Returns payment authorization and submission status.
Submission occurs with Apple Pay or Google Pay.Launches the platform wallet and completes payment.Returns wallet authorization result.
Successful submission completes.Locks the request and displays it as read-only in Appointment Details.Returns the finalized request state.
Back navigation occurs.Returns to the previous screen without submitting.Returns the unchanged request state.