0

The payments via some payment methods on a website are automatic -- you pay on a payment page via you bank card or PayPal and can see that a payment has been done and confirmed immediately.

For some payments methods the result or status can't be confirmed immediately. A user is supposed to pay and be notified by email. For instance, payments via BankTransfer. Or some others.

My question is:

how to create smooth, non-ambiguous UX page for the 2nd type of payments -- manual ones, that is?

When a user is redirected to a page where he sees the details for BankTransfer payment, what does he expect from that page in terms of buttons, navigation, text, links? Should there be only a text with Payment Details and a button "Return to home page"? Or what else?

Are there decent and good examples of such pages?

1

In general, user expected to be informed what is the next step in his transaction. In case of immediate payment he will receive receipt and delivery information. In case of long payment he should be informed that there is additional step exists - payment confirmation. Payment confirmation should have link to further step page with receipt and delivery terms. This is very general workflow. My answer is - user should be redirected to page with instructions how he should wait payment confirmation and what to do after this.

  • oh! also -- how would know at what moment I should purge customer's shopping cart? Normally I'd that after a payment has been confirmed. but in this case.... – Serenado May 24 '18 at 3:20
  • I think shopping cart should be purged after user initiated long payment - this is a kind of commit transaction, so this order is counted as processing. Unless you don't implement complex technology of order modification after payment started. – Serg May 24 '18 at 10:49
  • after user initiated long payment - - how would I know when it happens? – Serenado May 24 '18 at 11:16
  • User selects payment method and you know which payment method is immediate or long. Probably system generates event - 'Long payment started' which is processed in some way. – Serg May 24 '18 at 11:43
  • Ok. But how do I know when a user has actually paid via a long-processing time method? maybe he'd finally decide to pay in a week from a time when placed an order. – Serenado May 24 '18 at 16:15
0

The user will expect the same elements for the checkout process, except instead of showing the payment confirmation, the page should show the payment status. Also, it would be interesting if the user could create an account, for checking the status later. Here is an example of payment status.

  • my dear, how can it show the payment status or confirmation if the status/confirmation of a payment can't be determined in real time -- that's what my question is about! my question was also -- what buttons does a user expect on that page? – Serenado May 22 '18 at 2:41
  • Oh sorry, my answer wasn't clear enough. The payment status could be something like "The payment is pending" or "The payment is being processed" or "The payment will be confirmed in 48 hours". About the buttons, like in the example, If the payment is pending, and it is possible to cancel it, the user should have the option in this page. About navigation, text and other options, I don't see why it would be different from the confirmation page of other payment methods. – Aline May 22 '18 at 13:38
  • I think you don't understand. 1) of course it's not possible to cancel it because .... it's manually processed 2) on a normal payment page there's a button "Pay now". I click it, get charged, see that it's confirmed and get redirected to a "thank you" page. What should be instead on that "Pay manually" page? There can't be such a button "pay now" because payment, for instance, can be done via WireTransfer. – Serenado May 22 '18 at 15:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.