curl --request POST \
  --url https://api.petstoreapi.com/v1/orders/{id}/payment \
  --header 'Content-Type: application/json' \
  --data '
{
  "amount": "49.99",
  "currency": "GBP",
  "source": {
    "object": "card",
    "name": "J. Doe",
    "number": "4242424242424242",
    "cvc": "123",
    "expMonth": 12,
    "expYear": 2025,
    "addressLine1": "123 Fake Street",
    "addressLine2": "4th Floor",
    "addressCity": "London",
    "addressCountry": "gb",
    "addressPostCode": "N12 9XX"
  }
}
'

{
  "id": "2e3b4f5a-6b7c-8d9e-0f1a-2b3c4d5e6f7a",
  "amount": "49.99",
  "currency": "GBP",
  "source": {
    "object": "card",
    "name": "J. Doe",
    "number": "************4242",
    "cvc": "123",
    "expMonth": 12,
    "expYear": 2025,
    "addressCountry": "gb",
    "addressPostCode": "N12 9XX"
  },
  "status": "succeeded"
}

Payments

Pay Order

Process payment for an existing order.

Payment Workflow

Payment processing follows this workflow:

Create Order: First create an order using POST /orders (status: placed)
Submit Payment: Call this endpoint with payment details (card or bank account)
Payment Processing: The payment is processed with status processing
Payment Result:
- Success: Payment status becomes succeeded, order status updates to approved
- Failure: Payment status becomes failed, order remains placed and can be retried
Receipt: After successful payment, retrieve the receipt from the order details

Security Note: Sensitive payment data (like CVC codes) are writeOnly and never returned in responses. Card numbers and account numbers are masked when read.

POST

orders

{id}

payment

curl --request POST \
  --url https://api.petstoreapi.com/v1/orders/{id}/payment \
  --header 'Content-Type: application/json' \
  --data '
{
  "amount": "49.99",
  "currency": "GBP",
  "source": {
    "object": "card",
    "name": "J. Doe",
    "number": "4242424242424242",
    "cvc": "123",
    "expMonth": 12,
    "expYear": 2025,
    "addressLine1": "123 Fake Street",
    "addressLine2": "4th Floor",
    "addressCity": "London",
    "addressCountry": "gb",
    "addressPostCode": "N12 9XX"
  }
}
'

{
  "id": "2e3b4f5a-6b7c-8d9e-0f1a-2b3c4d5e6f7a",
  "amount": "49.99",
  "currency": "GBP",
  "source": {
    "object": "card",
    "name": "J. Doe",
    "number": "************4242",
    "cvc": "123",
    "expMonth": 12,
    "expYear": 2025,
    "addressCountry": "gb",
    "addressPostCode": "N12 9XX"
  },
  "status": "succeeded"
}

Path Parameters

string<uuid>

required

Unique identifier for the order

Body

application/json

Order payment information with polymorphic payment sources

amount

string

required

Payment amount (positive decimal)

Examples:

"49.99"

"100.50"

currency

enum<string>

default:USD

required

Three-letter ISO 4217 currency code (uppercase)

Available options:

USD,

EUR,

GBP,

CAD,

AUD

source

Bank Card · object

required

Payment source (card or bank account)

Bank Card
Bank Account

Show child attributes

Response

Payment successful

Order payment information with polymorphic payment sources

string<uuid>

required

Unique payment identifier

Example:

"2e3b4f5a-6b7c-8d9e-0f1a-2b3c4d5e6f7a"

amount

string

required

Payment amount (positive decimal)

Examples:

"49.99"

"100.50"

currency

enum<string>

default:USD

required

Three-letter ISO 4217 currency code (uppercase)

Available options:

USD,

EUR,

GBP,

CAD,

AUD

source

Bank Card · object

required

Payment source (card or bank account)

Bank Card
Bank Account

Show child attributes

status

enum<string>

required

Payment status

Available options:

PENDING,

PROCESSING,

SUCCEEDED,

FAILED,

CANCELLED

createdAt

string<date-time>

Payment creation timestamp

Create Chat Completion List Inventory

⌘I

Pet

Chat

Payments

Store

User

Webhooks

Pay Order

Payment Workflow

Path Parameters

Body

Response