It probably comes down to how many have actually added their cards to GPay and Apple pay, best to experiment and check if adding paypal improves your conversions
Hyperswitch is free to use for the first 10k transactions of the month. After that it costs $0.04 per transaction. It is a payment switch that comes pre integrated with major processors. So as a merchant your business relationship with processors like Stripe or Adyen remains the same
(I'm affiliated with this product)
I think there is a strong relationship between the average ticket size and payment experience. It is almost like it is the user's problem if the ticket size is high (hence the website need not necessarily invest in creating a good payment experience). Something like insurance websites.
The ones that really seem to think about the payment experience are the ones that have low to medium average ticket size and high transaction volumes. It is in the website's best interest to ensure each and every transaction goes through
True, it kind of depends on your current payment processor configuration.
For example if you find yourself in the need of accepting too many payment methods, you'll definitely benefit from the difference in fees for each method across processors
It also depends on your business focus. If you do not have the bandwidth to think beyond your core business, you might just be well off with a single processor
In that case I think it is just slightly more convenient to render a PCI compliant entity's frontend as an iframe inside your application and have it send the details directly to the processor's server, perhaps saves one additional hop