---
title: "POST /vet_payment_method"
method: POST
path: "/vet_payment_method"
tags: ["Payment Methods"]
---

# POST /vet_payment_method

`POST /vet_payment_method`

Validates whether a consumer has entered a valid ABA/routing number or card number. Use this endpoint when you want to validate payment method information before collecting additional details (e.g., in an IVR flow).</br></br>ACH routing numbers are validated using a table lookup against the Federal Reserve's database of valid routing numbers. Credit and debit cards are validated using the Luhn checksum algorithm. Submit only one of <code>payment_method_ach_aba_pii</code> or <code>payment_method_card_number_pii</code> per request.

## Request body

- union — Validates an ABA/routing number or card number. Submit only one of <code>payment_method_ach_aba_pii</code> or <code>payment_method_card_number_pii</code> per request. ACH validation uses a table lookup against the Federal Reserve database. Card validation uses the Luhn checksum algorithm.
  - object
    - `site_identifier` string, required — Identifies your client site.
    - `timestamp` string, required — The Unix Epoch time of the call
    - `version` string, required — The version of the API. This version must match the version associated with your API key pair.
    - `signature` string, required — The HMAC signature that is calculated by running your API Secret Key and the alphabetized, concatenated parameters of the request payload through the SHA256 message digest algorithm.
    - `payment_method_ach_aba_pii` string, required — The 9-digit ABA/routing number to validate.
  - object
    - `site_identifier` string, required — Identifies your client site.
    - `timestamp` string, required — The Unix Epoch time of the call
    - `version` string, required — The version of the API. This version must match the version associated with your API key pair.
    - `signature` string, required — The HMAC signature that is calculated by running your API Secret Key and the alphabetized, concatenated parameters of the request payload through the SHA256 message digest algorithm.
    - `payment_method_card_number_pii` string, required — The credit or debit card number (PAN) to validate. Validation uses the Luhn checksum algorithm.

## Response `200`

Payment Method Valid

- VetPaymentMethodResponse
  - `status` 'ok' | 'error' — The status of the validation request.
  - `errors` string[] — A list of error messages returned when validation fails.

## Other responses

- `400` — Payment Method Invalid

---

[API](https://skmtc.net/paynearme/apis/paynearme-api-v3-0.md) · [All operations](https://skmtc.net/paynearme/apis/paynearme-api-v3-0/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paynearme/paynearme-api-v3-0/revisions/44cba4f8b80f/schema)