Your own checkout
Let your customers pay in your own checkout, without a redirect to the myTU hosted payment page.
In your own checkout, you show the payment form or the wallet button yourself. Your customer stays on your website or in your app, and your server sends the payment to the myTU API. You control the full checkout experience, in exchange for more work than the hosted payment page.
What you can accept
Cards
Collect card details in your own form. Requires PCI DSS compliance.
Apple Pay
Show the Apple Pay button in your checkout.
Google Pay
Show the Google Pay button in your checkout.
For the payment methods you don't build into your checkout yourself, your customer can still pay on the hosted payment page. Show the method in your checkout, and send your customer straight to it on the hosted page. See Let your customer choose in your own checkout.
PCI DSS
How much card data reaches your systems depends on what you build:
| You build | Card data in your systems | PCI DSS |
|---|---|---|
| Apple Pay or Google Pay, encrypted payload | No. myTU decrypts the payment token. | Lowest impact |
| Apple Pay or Google Pay, decrypted payload | Yes. You decrypt the payment token with your own keys. | You must be PCI DSS compliant |
| A card form | Yes. Your customer enters the card details in your form. | You must be PCI DSS compliant |
Next steps
- Pick a payment method above and follow its guide.
- Go beyond the basics with pre-authorizations, saved cards and more.