Retrieve Payment Method
GET/payment-methods/:payment_method_id
Returns a single Payment Method.
Readable by the owner, an admin, or the account's onboarder (a merchant may read its individuals' payment methods; a partner its merchants'). This endpoint returns the full account number; the list endpoint exposes last4 only.
Request
Path Parameters
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
Payment Method's ID
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 500
Payment Methods retrieved
- application/json
- Schema
- Example (from schema)
Schema
- CardResponseFull
- BankAccountResponseDetail
- WalletResponseFull
- CryptoWalletResponseFull
Possible values: [success]
data
object
anyOf
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: [card, bank-account, wallet, crypto-wallet]
billing_details
object
Possible values: <= 255 characters
Name of the billing contact person
Possible values: <= 255 characters
Email Address
Possible values: non-empty and <= 20 characters
Phone Number
address
object
nullable
Address of the billing contact
Possible values: >= 2 characters and <= 2 characters
Two-letter code ISO 3166-1 country code
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Specifies if the payment method can be used as a destination in charges/transfers
Specifies if the payment method can be used as a source in charges/transfers
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Unix timestamp representing the date
card
object
expiration
object
Possible values: >= 2 characters and <= 2 characters
2 digit expiration month
Possible values: >= 4 characters and <= 4 characters
4 digit expiration year
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: [card, bank-account, wallet, crypto-wallet]
billing_details
object
Possible values: <= 255 characters
Name of the billing contact person
Possible values: <= 255 characters
Email Address
Possible values: non-empty and <= 20 characters
Phone Number
address
object
nullable
Address of the billing contact
Possible values: >= 2 characters and <= 2 characters
Two-letter code ISO 3166-1 country code
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Specifies if the payment method can be used as a destination in charges/transfers
Specifies if the payment method can be used as a source in charges/transfers
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Unix timestamp representing the date
bank-account
object
Bank instrument details. The list endpoint returns only the last 4 digits (last4) plus the routing_number. The single-resource detail endpoint (GET /payment-methods/{payment_method_id}) additionally returns the full account_number (see BankAccountResponseDetail). iban/sort_code/swift_bic sent at creation are never returned.
Full name on the bank account.
Whether the account holder is an individual or a business.
ISO 3166-1 alpha-2 country code of the bank.
The bank account type (e.g. checking, savings).
US routing number, when applicable.
Last 4 digits of the account number/IBAN. The full identifier is never returned.
Specifies is the bank account is a same day credit account
ISO 4217 currency code of the account.
Full bank account number. Returned only by this single-resource detail endpoint; the list endpoint (GET /payment-methods) returns last4 only. For a virtual account this is the deposit account number to fund via ACH.
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: [card, bank-account, wallet, crypto-wallet]
billing_details
object
Possible values: <= 255 characters
Name of the billing contact person
Possible values: <= 255 characters
Email Address
Possible values: non-empty and <= 20 characters
Phone Number
address
object
nullable
Address of the billing contact
Possible values: >= 2 characters and <= 2 characters
Two-letter code ISO 3166-1 country code
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Specifies if the payment method can be used as a destination in charges/transfers
Specifies if the payment method can be used as a source in charges/transfers
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Unix timestamp representing the date
wallet
object
available_balance
object
Money representation
Possible values: <= 9999999999
Amount expressed in cents. 1 USD should be submitted as 100 cents
ISO 4217 representation of the currency
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: [card, bank-account, wallet, crypto-wallet]
billing_details
object
Possible values: <= 255 characters
Name of the billing contact person
Possible values: <= 255 characters
Email Address
Possible values: non-empty and <= 20 characters
Phone Number
address
object
nullable
Address of the billing contact
Possible values: >= 2 characters and <= 2 characters
Two-letter code ISO 3166-1 country code
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Possible values: <= 255 characters
Specifies if the payment method can be used as a destination in charges/transfers
Specifies if the payment method can be used as a source in charges/transfers
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Possible values: <= 36 characters, Value must match regular expression ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
UUID v4
Unix timestamp representing the date
crypto-wallet
object
Crypto currency code following the CHAIN-TOKEN convention (e.g. BASE-USDC).
On-chain deposit address assigned once the wallet is provisioned. null until provisioning completes.
Possible values: [provisioned, external]
provisioned = platform-issued custodial wallet; external = customer-provided self-custodied address (sends to it are final).
Possible values: [200]
Possible values: [Successful request]
{
"status": "success",
"data": {},
"code": 200,
"message": "Successful request"
}
Access token is missing or invalid
Access denied
Payment method not found
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [not found]
Possible values: [404]
Failure reason
{
"status": "not found",
"code": 404,
"message": "Entity not found"
}
Payment Method not found
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [fail]
Possible values: [409]
Failure reason
{
"status": "fail",
"code": 409,
"message": "Entity with Id already exists"
}
Request failed due to invalid data provided
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [error]
Possible values: [422]
{
"status": "error",
"data": {
"dob": {
"day": "Value expected to be 'integer', 'string' given."
}
},
"code": 422,
"message": "cannot process the provided entity"
}
Server error