---
title: "Get Payment Method by Id"
method: GET
path: "/financials/payment-methods/{payment_method_id}"
tags: ["Payment Method"]
---

# Get Payment Method by Id

`GET /financials/payment-methods/{payment_method_id}`

Get a Payment Method record given the provided Payment Method ID.

## Path parameters

- `payment_method_id` integer, required

## Headers

- `x-api-key` string, required

## Response `200`

Payment Method info based on the supplied payment method identifier

- ResponsePaymentMethod — PaymentMethod data with error
  - `id` integer — Payment Method Id
  - `name` string — Name of the Payment Method
  - `client_id` integer — Id of the Client that the Payment Method is for
  - `client` string — Name of the client the Payment Method is for
  - `owner_client_id` integer — Owner Id of the Payment Method (if shared)
  - `owner_client` string — Owner of the Payment Method (if shared)
  - `shared_payment_method_id` integer — Id of the shared payment method
  - `payment_account_type_id` integer — Id of the Payment Account Type of the Payment Method
  - `payment_account_type` string — Payment Account Type of the Payment Method
  - `expiration_date` string, date — Date the Payment Method expires
  - `is_default` boolean — Indicates if the Payment Method is the Client's default Payment Method
  - `verification_status` string — Status of the verification for the Payment Method
  - `is_active` boolean — Determines if the Payment Method is active
  - `created` Created — Record creation data.
    - `created_by_id` integer — Unique ID of the user that created the record.
    - `created_by` string — Name of the user that created the record.
    - `created_on_datetime` string, date-time — Datetime on which the record was created.
  - `updated` Updated — Update info
    - `updated_by_id` integer — Unique ID of the user that last updated the record.
    - `updated_by` string — Name of the user that most recently updated the record.
    - `updated_on_datetime` string, date-time — Datetime on which the record was last updated.
  - `shared_clients` SharedPaymentMethodAPI[] — List of clients that share the Payment Method
    - `client_id` integer — Id of the client sharing the payment method
    - `client` string — Name of the client sharing the payment method
  - `wodify_validation_result` string — The purpose of this attribute is to save any UserException message, that is, and user friendly message that should be shown to the end user. All methods should have, just like service actions: - an UserException with Abort Transaction = Yes, and a Log Error = No - an AllExceptions with Abort Transaction = Yes, and a Log Error = Yes With this, any known issue that we don't consider an error log, like a business validation, we raise it to be catch in the UserException and we don't log it. Then, in the OnResponse of the full REST service, the Build_Response_JSON action will take care on the output json format. An Exception will have the default formatted error message. If its an AllException, it will log the error so that we can fix it. If its a UserException, it will deliver as an error but it won't log it as an error. A success output will not have this attribute, the Build_Response_JSON will remove it from the final output.

---

[API](https://skmtc.net/wodify/apis/leads.md) · [All operations](https://skmtc.net/wodify/apis/leads/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wodify/leads/revisions/974500ca0714/schema)