Retrieve an FX Quote

Retrieve an FX Quote object

Parameters

No parameters.

Returns

Returns an FX Quote object

GET /v1/fx_quotes/:id

Server-side language

curl https://api.stripe.com/v1/fx_quotes/fxq_1QKf8UET9NELqCotgW6CNTnm \
  -u "sk_test_BQokikJ...2HlWgH4olfQ2sk_test_BQokikJOvBiI2HlWgH4olfQ2:"

Response

{
  "id": "fxq_1QKf8UET9NELqCotgW6CNTnm",
  "object": "fx_quote",
  "created": 1731498806.6424642,
  "lock_duration": "hour",
  "lock_expires_at": 1731502406.5579598,
  "lock_status": "active",
  "rates": {
    "gbp": {
      "exchange_rate": 1.10167,
      "rate_details": {
        "base_rate": 1.12415,
        "fx_fee_rate": 0.02,
        "reference_rate": 1.12437,
        "reference_rate_provider": "ecb"
      }
    },
    "krw": {
      "exchange_rate": 0.000617274,
      "rate_details": {
        "base_rate": 0.000629871,
        "fx_fee_rate": 0.02,
        "reference_rate": 0.000629997,
        "reference_rate_provider": "ecb"
      }
    }
  },
  "to_currency": "chf",
  "usage": {
    "payment": null,
    "transfer": null,
    "type": "payment"
  }
}

List active FX Quotes

Returns a list of FX quotes that have been issued. The FX quotes are returned in sorted order, with the most recent FX quotes appearing first.

Parameters

No parameters.

More parameters

ending_beforestring

limitinteger

starting_afterstring

Returns

Returns a list of active FX Quote objects

GET /v1/fx_quotes

Server-side language

curl https://api.stripe.com/v1/fx_quotes \
  -u "sk_test_BQokikJ...2HlWgH4olfQ2sk_test_BQokikJOvBiI2HlWgH4olfQ2:"

Response

{
  "object": "list",
  "data": [
    {
      "id": "fxq_1QKhOFJNWfm6rTxStk9ZbHFc",
      "object": "fx_quote",
      "created": 1731507471.9745815,
      "lock_duration": "hour",
      "lock_expires_at": 1731511071.8779202,
      "lock_status": "active",
      "rates": {
        "krw": {
          "exchange_rate": 0.00054915,
          "rate_details": {
            "base_rate": 0.000560357,
            "fx_fee_rate": 0.02,
            "reference_rate": 0.000560469,
            "reference_rate_provider": "ecb"
          }
        },
        "usd": {
          "exchange_rate": 0.767475,
          "rate_details": {
            "base_rate": 0.783138,
            "fx_fee_rate": 0.02,
            "reference_rate": 0.783295,
            "reference_rate_provider": "ecb"
          }
        }
      },
      "to_currency": "gbp",
      "usage": {
        "payment": null,
        "transfer": null,
        "type": "payment"
      }
    },
    {
      "id": "fxq_1QAtdiIHwhphhlQlU0ckVq4L",
      "object": "fx_quote",
      "created": 1729171278.667021,
      "lock_duration": "day",
      "lock_expires_at": 1729257678.5269883,
      "lock_status": "active",
      "rates": {
        "gbp": {
          "exchange_rate": 1.10078,
          "rate_details": {
            "base_rate": 1.12325,
            "fx_fee_rate": 0.02,
            "reference_rate": 1.12347,
            "reference_rate_provider": "ecb"
          }
        }
      },
      "to_currency": "chf",
      "usage": {
        "payment": null,
        "transfer": null,
        "type": "payment"
      }
    }
  ],
  "has_more": false,
  "url": "/v1/fx_quotes"
}

Mandates

A Mandate is a record of the permission that your customer gives you to debit their payment method.

Endpoints

GET/v1/mandates/:id

Payment Intents

A PaymentIntent guides you through the process of collecting a payment from your customer. We recommend that you create exactly one PaymentIntent for each order or customer session in your system. You can reference the PaymentIntent later to see the history of payment attempts for a particular session.

A PaymentIntent transitions through multiple statuses throughout its lifetime as it interfaces with Stripe.js to perform authentication flows and ultimately creates at most one successful charge.

Related guide: Payment Intents API

Endpoints

POST/v1/payment_intents

POST/v1/payment_intents/:id

GET/v1/payment_intents/:id

GET/v1/payment_intents

POST/v1/payment_intents/:id/cancel

POST/v1/payment_intents/:id/capture

POST/v1/payment_intents/:id/confirm

POST/v1/payment_intents/:id/increment_authorization

POST/v1/payment_intents/:id/apply_customer_balance

GET/v1/payment_intents/search

POST/v1/payment_intents/:id/verify_microdeposits

Setup Intents

A SetupIntent guides you through the process of setting up and saving a customer’s payment credentials for future payments. For example, you can use a SetupIntent to set up and save your customer’s card without immediately collecting a payment. Later, you can use PaymentIntents to drive the payment flow.

Create a SetupIntent when you’re ready to collect your customer’s payment credentials. Don’t maintain long-lived, unconfirmed SetupIntents because they might not be valid. The SetupIntent transitions through multiple statuses as it guides you through the setup process.

Successful SetupIntents result in payment credentials that are optimized for future payments. For example, cardholders in certain regions might need to be run through Strong Customer Authentication during payment method collection to streamline later off-session payments. If you use the SetupIntent with a Customer, it automatically attaches the resulting payment method to that Customer after successful setup. We recommend using SetupIntents or setup_future_usage on PaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.