> ## Documentation Index > Fetch the complete documentation index at: https://docs.fintoc.com/llms.txt > Use this file to discover all available pages before exploring further. # List payment intents > Returns a paginated list of the payment intents of your organization, in the `live` or `test` mode of the API key used. **`v1`** ยท URL base `https://api.fintoc.com/v1` ## OpenAPI ````yaml reference/fintoc-api.json GET /payment_intents openapi: 3.1.0 info: title: fintoc-api version: v2026-02-01 servers: - url: https://api.fintoc.com/v1 security: [] paths: /payment_intents: get: tags: - Payment intents (cash only) summary: List payment intents description: >- Returns a paginated list of the payment intents of your organization, in the `live` or `test` mode of the API key used. operationId: payment-intents-list parameters: - name: since in: query required: false schema: type: string format: date-time example: '2021-01-01T00:00:00.000Z' description: >- ISO 8601 datetime. If present, Fintoc returns only payment intents created at or after this value. - name: until in: query required: false schema: type: string format: date-time example: '2021-01-31T00:00:00.000Z' description: >- ISO 8601 datetime. If present, Fintoc returns only payment intents created at or before this value. - name: status in: query required: false schema: type: string enum: - succeeded - rejected - failed - created - in_progress - pending - expired example: succeeded description: >- If present, Fintoc returns only payment intents with this status. `pending` is only available if your organization has the pending status enabled. - name: page in: query required: false schema: type: integer format: int32 description: Page number to retrieve. Starts at `1`. - name: per_page in: query required: false schema: type: integer format: int32 description: >- Number of payment intents per page. Defaults to `30`. The maximum is `300`. responses: '200': description: >- Paginated list of payment intents. The `Link` and `X-Total-Count` headers carry the pagination information. headers: Link: schema: type: string X-Total-Count: schema: type: integer content: application/json: examples: payment_intents_list: value: - id: pi_BO381oEATXonG6bj object: payment_intent amount: 100000 business_profile: null created_at: '2021-10-15T15:23:11.474Z' currency: CLP customer: null customer_email: jon.snow@example.com error_reason: null expires_at: null metadata: order_id: '9182' mode: live next_action: null payment_method: null payment_type: bank_transfer payment_type_options: {} recipient_account: holder_id: '111111111' institution_id: cl_banco_de_chile number: '123456789' type: checking_account reference_id: '90123712' sender_account: holder_id: '111111111' institution_id: cl_banco_estado number: '123456789' type: checking_account status: succeeded subscription: null transaction_date: '2021-10-15T15:24:15.474Z' widget_token: null schema: type: array items: $ref: '#/components/schemas/payment_intent' '400': description: >- Invalid request: the `status` is not one of the valid values, or `pending` is not enabled for your organization. content: application/json: examples: invalid_status: value: error: type: invalid_request_error code: invalid_enum param: status message: >- Invalid status: pending. Must be one of 'succeeded', 'rejected', 'failed', 'created', 'in_progress' or 'expired'. doc_url: https://docs.fintoc.com/reference/errors schema: $ref: '#/components/schemas/error_object' '401': description: Invalid or missing API key. content: application/json: examples: invalid_api_key: value: error: type: authentication_error code: invalid_api_key message: 'Invalid API Key: invalid-*oken' schema: $ref: '#/components/schemas/error_object' security: - api_key: [] components: schemas: payment_intent: type: object properties: id: type: string description: Unique identifier of the payment intent. example: pi_BO381oEATXonG6bj object: const: payment_intent description: Type of the object. Always `payment_intent`. amount: type: integer description: >- Amount of the payment intent, in the smallest unit of the currency (for example, `100000` for 100000 CLP, since CLP has no minor unit, or `7050` for 70.50 MXN). example: 100000 business_profile: type: - object - 'null' description: >- Profile of the business that collects the payment, when provided. `null` otherwise. properties: category: type: string description: Category of the business. name: type: string description: Name of the business. tax_id: type: string description: Tax identifier of the business. created_at: type: string format: date-time description: ISO 8601 timestamp of when the payment intent was created. example: '2021-10-15T15:23:11.474Z' currency: type: string enum: - CLP - MXN description: >- Three-letter ISO 4217 currency code of the payment intent. One of `CLP` or `MXN`. example: CLP customer: type: - object - 'null' description: >- Customer associated with the payment intent, when it was created from a checkout session with a customer. `null` otherwise. properties: id: type: string description: Unique identifier of the customer. object: const: customer description: Type of the object. Always `customer`. address: type: - object - 'null' description: Address of the customer. `null` when not provided. properties: city: type: string description: City of the address. country: type: string description: Country of the address. line1: type: string description: First line of the address. line2: type: string description: Second line of the address. postal_code: type: string description: Postal code of the address. state: type: string description: State of the address. created_at: type: string format: date-time description: ISO 8601 timestamp of when the customer was created. email: type: - string - 'null' description: Email address of the customer. metadata: type: object description: Set of key-value pairs attached to the customer. mode: type: string description: Mode of the customer. One of `live` or `test`. name: type: - string - 'null' description: Name of the customer. phone: type: - string - 'null' description: Phone number of the customer. tax_id: type: - object - 'null' description: Tax identifier of the customer. `null` when not provided. properties: type: type: string description: Type of the tax identifier, for example `cl_rut`. value: type: string description: Value of the tax identifier. customer_email: type: - string - 'null' description: >- Email address of the customer that receives payment notifications. `null` when not provided. example: jon.snow@example.com error_reason: type: - string - 'null' description: >- Reason why the payment failed, was rejected, or expired. `null` while the payment is in progress and when it succeeds. example: insufficient_funds expires_at: type: - string - 'null' format: date-time description: >- ISO 8601 timestamp of when the payment expires and can no longer be paid. Only set for cash payments; `null` otherwise. metadata: type: object description: Set of key-value pairs attached to the payment intent. example: order_id: '9182' mode: $ref: '#/components/schemas/mode' next_action: type: - object - 'null' description: >- Action the customer must complete to continue the payment, as reported by the widget. `null` when no action is pending. payment_method: type: - string - 'null' description: >- Identifier of the payment method used to pay, when the payment intent comes from a checkout session or a subscription. `null` otherwise. example: pm_1x7vKQ8oEATXonG6 payment_type: type: string description: Payment type used to pay, such as `bank_transfer` or `cash`. example: bank_transfer payment_type_options: type: object description: >- Options specific to the payment type. For card payments, the object contains a `card` object. For cash payments, the object contains a `cash` object with the `reference_number`, `barcode_url`, and `voucher_url` of the payment. For bank transfers, the object is empty. properties: card: type: object description: Details of the card payment. Present only for card payments. properties: authenticated_with_3ds: type: boolean description: >- If `true`, the cardholder completed 3-D Secure authentication for this payment. example: true bank: type: - string - 'null' description: >- Name of the bank that issued the card. `null` when the issuing bank is unknown. example: Banco de Chile brand: type: string description: Brand of the card. example: visa country: type: string description: >- Display name of the country where the card was issued, in English. example: Chile kind: type: string description: Kind of card. One of `credit`, `debit`, or `prepaid`. example: credit last_four_digits: type: - string - 'null' description: >- Last four digits of the card number. `null` when the digits are not available. example: '4242' wallet: type: - string - 'null' enum: - apple_pay - google_pay - null description: >- Digital wallet used for the card payment. One of `apple_pay` or `google_pay`. `null` for cards entered manually. example: apple_pay example: {} recipient_account: type: - object - 'null' description: Bank account that receives the payment. `null` for cash payments. properties: holder_id: type: - string - 'null' description: >- Tax identifier of the account holder (RUT in Chile, RFC in Mexico). example: '111111111' institution_id: type: - string - 'null' description: Identifier of the institution of the account. example: cl_banco_de_chile number: type: - string - 'null' description: Number of the account. In Mexico, the CLABE. example: '123456789' type: type: - string - 'null' description: >- Type of the account, such as `checking_account` or `sight_account`. example: checking_account required: - holder_id - number - type - institution_id reference_id: type: - string - 'null' description: >- Identifier of the transfer assigned by the institution. `null` until the transfer is executed. example: '90123712' sender_account: type: - object - 'null' description: >- Bank account the customer pays from. `null` until Fintoc identifies the sender. properties: holder_id: type: string description: >- Tax identifier of the account holder (RUT in Chile, RFC in Mexico). example: '111111111' institution_id: type: string description: Identifier of the institution of the account. example: cl_banco_estado number: type: string description: Number of the account. example: '123456789' type: type: string description: >- Type of the account, such as `checking_account` or `sight_account`. example: checking_account required: - holder_id - number - type - institution_id status: type: string enum: - created - failed - succeeded - rejected - in_progress - pending - expired description: >- Status of the payment intent. One of `created` (the customer has not started the payment), `in_progress` (the customer is paying), `succeeded` (the money reached the recipient account), `rejected` (the institution rejected the transfer), `failed` (the payment could not be completed), `expired` (the payment intent expired before being paid), or `pending` (the final status is not yet known; only used if your organization has the pending status enabled). example: succeeded subscription: type: - string - 'null' description: >- Identifier of the subscription that originated the payment intent. `null` for one-off payments. example: sub_dJOd4hcZby9XK1Lm transaction_date: type: - string - 'null' format: date-time description: >- ISO 8601 timestamp of when the institution executed the transfer. `null` until the transfer is executed. example: '2021-10-15T15:24:15.474Z' widget_token: type: - string - 'null' description: >- Token used to initialize the Fintoc widget for this payment intent. Only returned when the payment intent is created; `null` in every other response. example: pi_BO381oEATXonG6bj_sec_aBcDeFgHiJkLmNoP required: - id - object - amount - created_at - currency - customer - customer_email - error_reason - expires_at - metadata - mode - next_action - payment_method - payment_type - payment_type_options - recipient_account - reference_id - sender_account - status - subscription - transaction_date - widget_token error_object: type: object properties: error: type: object description: Details of the error that caused the request to fail. properties: code: type: string description: >- Machine-readable code identifying the specific error, for example `invalid_api_key`. Not returned by every error. example: invalid_api_key doc_url: type: string description: >- URL of a documentation page with more details about the error. Not returned by every error. example: https://docs.fintoc.com/reference/errors message: type: string description: Human-readable message describing the error. example: 'Invalid API Key: invalid-*oken' param: type: - string - 'null' description: >- Name of the request parameter that caused the error. `null` when the error cannot be tied to a single parameter, and not returned by every error. example: amount type: type: string description: >- Category of the error, for example `invalid_request_error`, `authentication_error`, or `api_error`. example: invalid_request_error required: - type - message mode: type: string enum: - test - live description: >- Mode of the object. `live` objects use real institution data, `test` objects use fake data for integration testing. example: live securitySchemes: api_key: type: apiKey name: Authorization in: header ````