{"id": "cs_li5531onlFDi235",
    "mode": "test",
    "amount": 350000,
    "object": "checkout_session",
    "status": "finished",
    "currency": "CLP",
    "metadata": {},
    "cancel_url": "https://merchant.com/987654321",
    "created_at": "2026-01-13T18:48:25Z",
    "expires_at": "2026-01-14T18:48:25Z",
    "success_url": "https://merchant.com/success",
    "redirect_url": "https://checkout.fintoc.com/checkout_session_01HXY3Z7X5YQ54V8G2E1KJQAVF",
    "session_token": null,
    "customer_email": null,
    "customer": {
      "name": "Felipe Castro",
      "email": "name@example.com",
      "metadata": {},
      "tax_id": {
        "type": "cl_rut",
        "value": "12088191"
      }
    },
    "payment_methods": [
      "payment_intent"
    ],
    "business_profile": {},
    "payment_resource": {
      "payment_intent": {
        "id": "pi_38DNJo3rbvGUzKFvCGZ6dxR1Kxx",
        "mode": "test",
        "amount": 350000,
        "object": "payment_intent",
        "status": "succeeded",
        "currency": "CLP",
        "metadata": {},
        "created_at": "2026-01-13T18:48:31Z",
        "expires_at": "2026-01-14T18:48:25Z",
        "error_reason": null,
        "payment_type": "bank_transfer",
        "reference_id": null,
        "widget_token": null,
        "customer_email": null,
        "sender_account": {
          "type": "checking_account",
          "number": "813990168",
          "holder_id": "415792638",
          "institution_id": "cl_banco_falabella"
        },
        "business_profile": {},
        "transaction_date": null,
        "recipient_account": null,
        "payment_type_options": {}
      }
    },
    "payment_method_options": {}
  }

Attribute	Type	Description
`id`	`string`	Unique identifier for the Checkout Session
`created_at`	`string`	`Checkout Session`'s creation date, using ISO 8601
`object`	`string`	Identifier for the type of object. Its value for `Checkout Session` will always correspond to `checkout_session`
`currency`	`string`	Currency ISO code. For now, we only support CLP and MXN.
`amount`	`integer`	Amount to pay, represented as an integer. This value must always be greater than 0
`customer_email`	`string`	A customer email linked to a `Checkout Session`. This is used to notify a user in case of a refund. If you plan on using the refunds product, you must include this field in your request If you create a session without providing a `customer_email`, this field will be `null` in the response and no emails will be sent for that Checkout Session.
`customer_data`	`hash`	Optional data of the customer of the checkout session.
`expires_at`	`string`	UTC timestamp in ISO 8601 format that indicates when the session will expire. It must be at least 10 minutes after the creation time. By default, it is set to 24 hours after the payment session is created.
`mode`	`string`	Indicates whether the `Checkout Session` is in `live` mode or in `test` mode.
`session_token`	`string`	Temporary token to configure the widget. Will be `null` if `success_url` and `cancel_url` are sent when creating the session.
`status`	`string`	Session status. Can be either `created`, `in_progress`, `finished`or `expired`
`success_url`	`string`	URL to redirect the user in case of payment succeeded.
`cancel_url`	`string`	URL to redirect the user in case they decide to cancel the payment and return to your website.
`redirect_url`	`string`	URL to redirect the user to complete the payment using the Fintoc widget.
`metadata`	`hash`	Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. If you create a payment without providing `metadata`, this field will be `null` when receiving notifications about the final status.
`payment_resource`	`object`	Payment resource associated to the session once the payment is finished. If the session has not finished or expired, this field will be `null`
`payment_method_options`	`hash`	Optional array of settings for each available Payment Method
`payment_methods`	`array`	Optional definition of the available payment method(s) for the session. Methods current available are `payment_intent` (bank transfers) and `card`
`business_profile`	`hash`	Optional object to identify enrolled merchants for category-based pricing.

Customer Object

Use this object to send data of the customer of the checkout session, like the tax_id (RUT in Chile), so Fintoc can display only the available payment methods for that specific customer, such as verifying if the amount exceeds the transaction limit for a selected bank in the payment initiation method.

Attribute	Type	Description
`tax_id`	`object`	Required object that identifies the customer at a fiscal or regulatory level. It includes a `type` field indicating the format or country-specific identifier (for example, "`cl_rut`" for Chilean RUT) and a `value` field containing the actual tax identification number as a string.
`name`	`string`	Optional full name of the customer.
`email`	`string`	Optional customer email linked to a Checkout Session. This is used to notify a user in case of a refund.
`metadata`	`object`	Optional custom data that can store additional information about the customer (e.g., internal IDs, CRM references, or tags)

Payment Intent Options

Use these options to configure the Payment Intent Payment Method when creating a Checkout Session

Attribute

Type

Description

recipient_account

string

Object that points to the recipient account. Take a look at the Recipient Acccount object table below to learn more. If you use Fintoc Collects for payments, omit this object during payment creation for better stability.

sender_account

string

Object that points to the sender account. Take a look at the Sender Acccount object table below to learn more.

When you receive final payment status notifications, sender_account may be null if the user abandoned the payment before specifying a sender account.

Recipient Account Object

Attribute	Type	Description
`holder_id`	`string`	Identifier of the owner of the account. In Chile, the `value` corresponds to a RUT and in Mexico it's either an RFC or CURP. The `editable` field indicates whether the user is allowed to change the preset username or not.
`number`	`string`	Account number. Does not include hyphens or prefixed zeros
`type`	`string`	Account type. It can be `checking_account` or `sight_account`
`institution_id`	`string`	Account's institution `id`. You can learn more about institutions and their `id`s here

Sender Account Object

Attribute	Type	Description
`holder_id`	`object`	Identifier of the owner of the account. In Chile, it corresponds to a RUT and in Mexico it's the user's phone number.
`institution_id`	`string`	Only for CL 🇨🇱 Account's institution `id`. You can learn more about institutions and their `id`s here

Business Profile Object

Attribute	Type	Description
`name`	`string`	Enrolled merchant´s name. If set, will be shown as the "Recipient" on the succeeded payment screen.
`category`	`string`	Identifier of the category of the enrolled merchant. In Chile, it corresponds to a 6 character SII activity code.
`tax_id`	`string`	Enrolled merchant's tax identifier. In Chile, it corresponds to a RUT.