--- title: "Customer Payment Methods" description: "An overview of customer payment methods, their public fields, and the operations used to manage them." type: "mcp_overview" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomerPaymentMethod.md" --- # RevCent MCP Overview: Customer Payment Methods A Customer Payment Method is a reusable payment reference belonging to a customer. Use it to review available methods, manage their enabled/default status, or select a saved method in an operation that supports it. ## Categories and display details | Category | Method | Rail | Display object | |---|---|---|---| | `card` | `card` | `card` | `card` | | `digital_wallet` | `apple_pay` or `google_pay` | `card` | `digital_wallet` | | `bank_account` | `ach` | `ach` | `ach` | Retrieval describes these categories. `AddCustomerPaymentMethod` currently accepts cards only. Do not infer that an operation accepts every category merely because retrieval can describe it. Each method has its own `id` and owning `customer_id`. Retrieval can include `enabled`, `is_default`, and creation/update Unix timestamps in seconds. Exactly one category-specific display object is included for a method; handle absent optional fields. Card display details include the network, last four digits, funding source, and expiration month/year. The returned expiration year has four digits. Wallet display digits may identify a tokenized wallet number rather than the physical card. Bank-account display details can include the bank name, account type, account-holder type, and the last four digits of account and routing numbers. Full card numbers, card security codes, complete account numbers, and wallet credentials are not returned. A card method may also expose its associated public `customer_card_id`. Use the method's `id` as `payment_method_id` in these routes; do not rename response fields. ## Operations | Operation | Purpose | |---|---| | [GetCustomerPaymentMethods](https://revcent.com/documentation/markdown/mcp/operation/GetCustomerPaymentMethods.md) | Returns the reusable payment methods associated with a customer. Sensitive credentials and complete account or card numbers are never returned. | | [AddCustomerPaymentMethod](https://revcent.com/documentation/markdown/mcp/operation/AddCustomerPaymentMethod.md) | Adds a reusable payment method to an existing customer. Card payment methods are currently supported. | | [GetCustomerPaymentMethod](https://revcent.com/documentation/markdown/mcp/operation/GetCustomerPaymentMethod.md) | Returns a specific reusable payment method associated with a customer. Sensitive credentials and complete account or card numbers are never returned. | | [EnableCustomerPaymentMethod](https://revcent.com/documentation/markdown/mcp/operation/EnableCustomerPaymentMethod.md) | Enables a reusable payment method so it can be selected for future payments. | | [DisableCustomerPaymentMethod](https://revcent.com/documentation/markdown/mcp/operation/DisableCustomerPaymentMethod.md) | Disables a reusable payment method so it cannot be selected for future payments. | | [SetDefaultCustomerPaymentMethod](https://revcent.com/documentation/markdown/mcp/operation/SetDefaultCustomerPaymentMethod.md) | Sets the selected payment method as the customer's default for its payment-method category. | | [DeleteCustomerPaymentMethod](https://revcent.com/documentation/markdown/mcp/operation/DeleteCustomerPaymentMethod.md) | Removes a reusable payment method from the customer's available payment methods. | All seven operations are in the MCP profile. Addition is also available to AI Voice Agents; retrieval and the enable, disable, default, and delete operations are also available to AI Assistants. Consult the selected profile when configuring an agent's operations. ## Finding and managing a method Start with a known customer ID, or find the customer through `SearchCustomers` or `GetCustomer`. Call `GetCustomerPaymentMethods` with that customer ID, review the returned methods, and use a returned method ID for subsequent actions. There is no separate Customer Payment Method search operation or card-specific search filter on this list. List responses put individual methods in `results[]`. A detail response is flat. Mutation responses return the customer and payment-method IDs rather than full credentials. Both customer and method identifiers belong in the URL for HTTP requests; MCP arguments include them alongside any body fields. `enabled` controls availability for future payments. `is_default` identifies the default within a category. Enabling a method and setting it as default are separate actions. When adding a card, `set_as_default` is optional and defaults to false; the customer's first card is set as default. ## Using a saved card for a sale Where supported, provide the method ID in the sale request's top-level `payment_method_id`. It is optional: provide it to select a specific method instead of the customer's default. For an existing pending sale, omission preserves its current payment selection. `CreateSale` and `CreatePendingSale` require `customer_id` when an explicit method is selected. Do not put this selector inside `credit_card`, and do not combine an explicit selector with a new `credit_card` input. The AI sale profiles accept saved cards for this selector. Their exclusion of wallet sale inputs does not remove wallet display information from Customer Payment Method retrieval. MCP CreateSale and ProcessPendingSale support credit card, PayPal, offline, and check payment types; Assistant and Voice versions support credit card only. The saved-card selector applies to credit-card payment. Consult the current operation schema for the request being made. ## Related documentation - [Customer Payment Method ecosystem item](https://revcent.com/documentation/markdown/ecosystem/item/CustomerPaymentMethod.md) - [Customer overview](https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomer.md) For reporting, use the published BigQuery dataset and its actual table/field names. The Customer Payment Method API names do not imply that warehouse tables or historical retrieval fields have been renamed. --- Document Parent Directory * [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.