Payment-settings Today

Even experienced operators make errors here. Avoid these pitfalls:

Payment Settings

Goal: Allow users (e.g., merchants, customers with saved payment methods) to manage their payment preferences, saved cards/bank accounts, default payment method, and billing info.

Key capabilities:

---

Backend processes must routinely scan for orphaned payment tokens (tokens associated with deleted user accounts) to maintain data hygiene and reduce liability.

---

If you are paying for a subscription or making a one-time purchase, you may need to add a new card or bank account.

You can edit existing cards to update expiration dates or billing addresses without deleting the profile. payment-settings

Under PSD2 (Europe) and similar global regulations, changing payment settings often qualifies as a "high-risk" action.

// types/payment.ts
export enum PaymentMethodType 
CARD = 'card',
BANK_ACCOUNT = 'bank_account',

export interface BillingAddress 
line1: string;
line2?: string;
city: string;
state: string;
postalCode: string;
country: string;
 Even experienced operators make errors here
export interface PaymentMethod 
id: string;
type: PaymentMethodType;
last4: string;
expiryMonth?: number;
expiryYear?: number;
brand?: string; // Visa, Mastercard, etc.
bankName?: string;
isDefault: boolean;
billingAddress: BillingAddress;

export interface PaymentSettings 
defaultPaymentMethodId: string;
paymentMethods: PaymentMethod[];
emailReceipts: boolean;
smsNotifications: boolean;