Skip to content
This repository has been archived by the owner on Jul 8, 2020. It is now read-only.

"Native Checkout" method support #8

Open
manospsyx opened this issue Jul 11, 2016 · 1 comment
Open

"Native Checkout" method support #8

manospsyx opened this issue Jul 11, 2016 · 1 comment

Comments

@manospsyx
Copy link
Member

manospsyx commented Jul 11, 2016

Ref: https://github.com/VivaPayments/API/wiki/Native-Checkout

https://support.vivawallet.com/hc/en-us/articles/201895281-What-is-the-difference-between-Redirect-and-Native-Checkout-

Native Checkout allows you to create a custom payment form, so that your customers never leave your page for making a card payment. This process is fully PCI-DSS compliant, as sensitive card data never reach your server.

Native Checkout, only allows you to accept card payments from a customer. You are therefore missing out on the Cash, Pay@Home and VivaWallet alternatives. To give additional payment options to your customers, we recommend using the ‘Redirect’ method instead.

Native Checkout seems to support payment tokens. Since WC 2.6 added support for tokens, this could be a very welcome feature for shop admins who don't care about missing out on the Cash, Pay@Home and VivaWallet payments (available with Redirect Checkout method only).

@mattyza a major feature to keep in mind for v1.1, possibly along with #5 .

@manospsyx manospsyx added this to the v1.1 milestone Jul 11, 2016
@manospsyx manospsyx self-assigned this Jul 11, 2016
@tcrosswell
Copy link

It would be great to see native checkout

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants