BUILT AROUND YOUR CONTROL
Your cards deserve
a careful touch.
CardTend is in prelaunch testing. These are the controls implemented in the service; they are not a claim of independent certification or completed production validation.
Secure card collection
Card details are entered on Stripe’s hosted checkout. CardTend stores processor references and limited card metadata, including the last four digits. We do not offer fields for full card numbers or security codes.
One card for each schedule
We verify the saved method is a supported US credit card and bind the schedule to that method. Unverified funding and debit cards are rejected before activation. A decline stops automatic attempts; there is no customer-level backup card to charge silently.
Payment results are verified
A redirect alone does not mark a payment successful. The server checks the processor’s payment record, selected method, amount, and environment. Each billing period has a durable attempt record, so interrupted responses can be checked without starting a second payment for that period.
Account access
Customer sign-in uses short-lived, one-time email codes and signed, HTTP-only session cookies. Server-side ownership checks protect account records. Sign out when using a shared device and protect access to your email account.
Report a concern
Email martini-doubler7g@icloud.com with the affected page and a description. Avoid including other customers’ data, full card numbers, security codes, or active sign-in codes. We will review the report.