Payment Method
Get customer's payment methods
API documentation
User
Tenant
Feature
Entitlement
User & permissions
Settings
- Settings
- Media
- Webhook
- Notification
Payment
- Payment Method
- Transaction
- SEPA XML
- Open Banking
- Bank Account Transaction
Customer
- Customer
- Customer Address
- Customer Email
- Customer Settings
- Customer Otp
Billing
- Invoice
- Invoice Position Item
- Billing Run
Dunning
- Dunning Document
- Dunning Rule
Subscription
- Subscription
- Subscription Item
- Subscription Measurement
- Billing Group
Offers
- Offer
- Offer Recipient
- Offer Template
Catalogue
- Unit
- Measurement
- Product
- Product Family
- Price Plan
- Coupon
Checkout
- Checkout Link
- Cart
Accounting
Payment Method
Get customer's payment methods
Get customer’s payment methods.
Required permissions:payment-method:read, customer:payment-method:readGET
/
customers
/
{customerId}
/
payment-methods
Authorizations
Value for the Authorization header parameter.
Path Parameters
PaymentMethod identifier
Query Parameters
The collection page number
The number of items per page
Required range:
0 < x < 100Response
200 - application/json
The card data of the payment method, if the type is "card"
Available options:
wallet, sepa_debit, stripe, fake_provider, paypal, bank_transfer, go_cardless, testing The sepa mandate data of the payment method, if the type is "sepa_debit"
The sepa mandate of the payment method, if the gatewayName is "payment_sepa"
The reference of the mandate
The type of the mandate
Possible values:
CORE: The core scheme is used for payments between consumers and companiesB2B: The B2B scheme is used for payments between companies. No refund is possibleCOR1: The COR1 scheme is used for payments between consumers and companies. The payment is processed faster than with the core scheme
Available options:
CORE, B2B, COR1 The sequence type of the mandate
Possible values:
FRST: The sepa mandate is used for the first time for a recurring paymentRCUR: The sepa mandate was already used the first time and is now used for recurring paymentsFNAL: The sepa mandate is used for the last time for a recurring paymentOOFF: The sepa mandate is only allowed to be used for one payment
Available options:
FRST, RCUR, FNAL, OOFF The status of the mandate
Possible values:
active: The mandate is active and can be used for paymentsrevoked: The customer has revoked the mandate or a payment was rejected by the bank. The mandate can not be used for payments anymore
Available options:
active, revoked Available options:
checkout, customerfront, api, add_link Available options:
active, action_required, expired, revoked, gateway_unconfigured Available options:
sepa_debit, card, paypal, bank_transfer, wallet, fake_provider Was this page helpful?