Get all Payment Methods for a Merchant

Retrieves a paginated data array of all non-deleted payment methods associated with a merchant by default.

Retrieve all payment methods associated with a merchant account. This includes active and inactive payment methods and provides merchants the ability to manage their stored payment methods effectively.

This endpoint supports filtering, sorting, and pagination for efficient data handling. It also includes integration with the Account Updater feature for merchants who have this capability enabled.

Key Features

credit-card
Complete Payment Method Access

Retrieves all non-deleted payment methods associated with the merchant account

filter
Advanced Filtering

Supports filtering by status, type, and creation date for precise data retrieval

sync-alt
Account Updater Integration

Automatic payment method updates based on card brand notifications


Usage Guide

searchFiltering Options

Status Filtering

  • Use the status parameter to filter payment methods by active or deleted status
  • To retrieve soft-deleted payment methods updated by the Account Updater, set status=deleted

Additional Filters

  • Filter by payment method type
  • Filter by creation date range
  • Combine multiple filters for precise results
bellAccount Updater Events

If Account Updater is enabled on the merchant's account, the following events can trigger updates to payment methods:

ReplacePaymentMethod
Occurs when a payment method's number and/or expiration date is updated by the card issuer.

ContactCardHolder
Indicates the account needs to be updated, but the issuer didn't provide updated values.

ClosePaymentMethod
Marks a payment method as inactive and soft-deletes it when the card is no longer valid.

undoRe-enabling Closed Payment Methods

Payment methods closed by Account Updater's ClosePaymentMethod event can be re-enabled by setting the deleted_at property to null.

Important: Only re-enable a payment method if you have verified it is still valid and should not have been deleted.


Response Structure

CodeResponseReason
200SuccessReturns a paginated list of payment method objects.
400Bad RequestInvalid query parameters.
401UnauthorizedAuthentication failed.
500Internal Server ErrorAn unexpected error occurred on the server.

Important Considerations

info-circleAccount Updater Integration Details

Payment methods updated via the Account Updater feature may include additional metadata:

  • Updated Reason: Explains why the update occurred (e.g., expiration date changed)
  • Updated By: Indicates that the update was triggered by the Account Updater
  • Update Timestamp: Shows when the automatic update was processed
databaseData Management

Soft-Deleted Methods
Payment methods marked as deleted by ClosePaymentMethod are not permanently erased and can be retrieved by filtering with status=deleted.

Default Sorting
Payment methods are ordered by created_at in descending order (newest first) unless specified otherwise.

Pagination
Large result sets are automatically paginated for optimal performance.

shield-altSecurity & Compliance

PCI DSS Compliance
Ensure your application complies with PCI DSS standards when handling or displaying payment method information.

Data Protection
Sensitive payment method data is tokenized and encrypted in transit and at rest.

Access Control
Only authenticated merchants can access their own payment method data.

Query Params
int32
Defaults to 20

Used to indicate how many records you want to fetch per page. The maximum is 200 and the minimum is 1. Defaults to 20.

string
enum

Used to filter results by the account updater last event.

Allowed:
date

Used to filter results that have the au_last_event_at greater than or equal to the given datetime value.

date

Used to filter results that have the au_last_event_at less than or equal to the given datetime value.

string
enum
Defaults to all

Used to filter results by the payment method's status.

Allowed:
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json