A payment method is a stored representation of how a customer intends to pay, such as a card, bank account, or digital wallet. It holds the necessary billing details and can be attached to a member for future one-time or recurring charges. This lets you reuse the same payment credentials across multiple payments.
Required permissions:
member:payment_methods:readThe app API key from an app from the /dashboard/developer page
The ID of the PaymentMethod
"payt_xxxxxxxxxxxxx"
The ID of the Member associated with the PaymentMethod
"mber_xxxxxxxxxxxxx"
A successful response
A stored payment method used to process payments. This could be a credit/debit card, bank account, PayPal wallet, etc.
The ID of the payment method
"payt_xxxxxxxxxxxxx"
The date and time the payment method was created
"2023-12-01T05:00:00.401Z"
The payment method type of the payment method
acss_debit, affirm, afterpay_clearpay, alipay, alma, amazon_pay, apple_pay, au_becs_debit, bacs_debit, bancontact, billie, blik, boleto, card, cashapp, crypto, eps, fpx, giropay, google_pay, grabpay, ideal, kakao_pay, klarna, konbini, kr_card, link, mobilepay, multibanco, naver_pay, nz_bank_account, oxxo, p24, pay_by_bank, payco, paynow, pix, promptpay, revolut_pay, samsung_pay, satispay, sepa_debit, sofort, swish, twint, us_bank_account, wechat_pay, zip, bizum, capchase_pay, kriya, mondu, ng_wallet, paypay, sequra, scalapay, vipps, custom, customer_balance, gopay, mb_way, ng_bank, ng_bank_transfer, ng_card, ng_market, ng_ussd, paypal, payto, qris, rechnung, south_korea_market, kr_market, shopeepay, upi, sunbit, netbanking, id_bank_transfer, demo_pay, shop_pay, sezzle, coinbase, splitit, platform_balance, apple, venmo, unknown The card data associated with the payment method, if its a debit or credit card.