1. Your choice
By actively accepting this authorization, the Merchant asks PayTR to create or return provider card tokens and allows TapLoyal to retain those tokens for the Merchant account. Declining this authorization does not itself prevent a one-time purchase, but card details may need to be entered again for a later payment.
2. Card data sent to PayTR
Raw primary account number (PAN), CVV, and card-expiry values are submitted from the browser to PayTR for payment and tokenization. TapLoyal does not store those raw values.
PayTR processes the card data under its own payment-service and security responsibilities. Issuer, network, authentication, and provider rules continue to apply.
3. What TapLoyal retains
After a successful provider response, TapLoyal may retain encrypted provider tokens and masked card metadata needed to identify and manage the saved payment method. Masked metadata is not a substitute for a full card number and cannot be used outside the provider flow as raw card data.
4. Permitted use
A saved method may be presented for a future Merchant-initiated TapLoyal checkout. It may be used for automatic renewal only when the Merchant has also accepted a separate Recurring Payment Authorization that remains applicable to the subscription.
Card-storage consent alone never authorizes a charge, a plan change, or recurring billing.
5. Authentication and CVV
A card issuer, card network, or PayTR may still require CVV entry, 3-D Secure, or another verification step. Saving a card does not guarantee that future unattended or merchant-initiated payments will be permitted or approved.
6. Withdrawal and removal
An authorized Merchant user may request removal through an available payment-method control or by contacting info@taployalapp.com. Removal prevents future TapLoyal use of that saved method after the request is processed, but does not reverse a charge already submitted or cancel a subscription by itself.
7. Token lifecycle
Provider tokens may expire, be rotated, become invalid, or be removed under PayTR, issuer, or card-network rules. TapLoyal may mark a method unavailable when a provider response indicates that it can no longer be used. A replacement method requires a new authorization.
8. Security and privacy
TapLoyal protects retained provider tokens with encryption and access controls. Payment and token metadata is processed for checkout, subscription administration, security, support, accounting, dispute handling, and legal obligations as described in the Privacy Notice.
9. Consent record and contact
TapLoyal records this document's version with the authorization so the text accepted by the Merchant can be identified. Questions or removal requests may be sent to info@taployalapp.com. Never send raw card data, CVV, passwords, or authentication codes by email.
Contact us
Questions about this document? Contact our team at