2 added 4 characters in body
source | link

I am designing a series of multi-step transactional forms which appear in the context of a web page with a progress bar, site header, footer, nav etc. Each form contains a payment step. There are two approaches for displaying the payment step: - take the user to the bank's payment page to fill out credit card details. The page doesn't retain the progress bar, header, footer, logo etc but may display the bank's logo - make the payment screen appear in the context of the website with progress bar, site header, logo etc all retained. The bank handles the payment securely.

  • take the user to the bank's payment page to fill out credit card details. The page doesn't retain the progress bar, header, footer, logo etc but may display the bank's logo
  • make the payment screen appear in the context of the website with progress bar, site header, logo etc all retained. The bank handles the payment securely.

What are the pros and cons of each approach from a usability perspective? Important factors include user orientation and the user's sense of trust in the payment mechanism.

I am designing a series of multi-step transactional forms which appear in the context of a web page with a progress bar, site header, footer, nav etc. Each form contains a payment step. There are two approaches for displaying the payment step: - take the user to the bank's payment page to fill out credit card details. The page doesn't retain the progress bar, header, footer, logo etc but may display the bank's logo - make the payment screen appear in the context of the website with progress bar, site header, logo etc all retained. The bank handles the payment securely.

What are the pros and cons of each approach from a usability perspective? Important factors include user orientation and the user's sense of trust in the payment mechanism.

I am designing a series of multi-step transactional forms which appear in the context of a web page with a progress bar, site header, footer, nav etc. Each form contains a payment step. There are two approaches for displaying the payment step:

  • take the user to the bank's payment page to fill out credit card details. The page doesn't retain the progress bar, header, footer, logo etc but may display the bank's logo
  • make the payment screen appear in the context of the website with progress bar, site header, logo etc all retained. The bank handles the payment securely.

What are the pros and cons of each approach from a usability perspective? Important factors include user orientation and the user's sense of trust in the payment mechanism.

1
source | link

Payment screens as part of a multi-step form

I am designing a series of multi-step transactional forms which appear in the context of a web page with a progress bar, site header, footer, nav etc. Each form contains a payment step. There are two approaches for displaying the payment step: - take the user to the bank's payment page to fill out credit card details. The page doesn't retain the progress bar, header, footer, logo etc but may display the bank's logo - make the payment screen appear in the context of the website with progress bar, site header, logo etc all retained. The bank handles the payment securely.

What are the pros and cons of each approach from a usability perspective? Important factors include user orientation and the user's sense of trust in the payment mechanism.