For high frequency payment flows, like ride sharing or delivery apps, you can allow your user to save a Payment Method (a card o a bank account), so their next payments will have less steps.

There are three steps to save a user's payment method using Fintoc:

1. On your backend, create a Checkout Session using your Secret Key with the flow: setup
2. Redirect your user to complete the flow on the Fintoc-hosted page
3. Handle post-payments events to save the payment_method of your customer
4. Create a Checkout Session of flow: payment for that customer with the id of the saved payment_method

Create a session

The Checkout Session object represents your intent to save a payment method and/or collect a payment.

Using your Secret Key, create a Checkout Session from your backend with the flow: setup:

curl --request POST "https://api.fintoc.com/v2/checkout_sessions" \
  --header "Authorization: YOUR_SECRET_API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "flow": "setup",
    "currency": "CLP",
    "success_url": "https://merchant.com/success",
    "cancel_url": "https://merchant.com/cancel",
    "customer_data": {
      "email": "[email protected]"
    },
    "metadata": {}
  }'

📘

Send the payment_method_options to pre select a bank for your user

You have the option create the Checkout Session in Fintoc with an specific bank sending its institution_id inside the sender_account of the payment_method_options, so your user will only be able to save a bank account of that specific institution. You can also send the RUT of the user as the holder_id, so it will be already filled on the flow.

It is recommended when you ask your user to decide the bank on your flow, before creating the session in Fintoc. So the user will not have to select bank twice.

Response when creating a Checkout Session

After creating a session, you receive a redirect_url that you must use to redirect your user.

Handle post-session events

Always use webhooks to determine the final outcome. Users may close the tab, lose connection, or never reach your success_url.

Checkout Session events

• checkout_session.finished

  • Sent when a Checkout Session reaches a final successful state.
  • For flow: setup, this will must include customer and payment_method so you can store them for future charges.
  • For flow: payment, it must include the payment outcome, and if the user opted in, include the payment_method.id

  Example payload:

  JSON

  {
    "id": "evt_a4xK32BanKWYn",
    "object": "event",
    "type": "checkout_session.finished",
    "data": {
      "id": "cs_li5531onlFDi235",
      "object": "checkout_session",
      "mode": "test",
      "flow": "setup",
      "status": "finished",
      "amount": 350000,
      "currency": "CLP",
      "metadata": {},
      "cancel_url": "https://merchant.com/987654321",
      "success_url": "https://merchant.com/success",
      "redirect_url": "https://checkout.fintoc.com/checkout_session_01HXY3Z7X5YQ54V8G2E1KJQAVF",
      "created_at": "2026-01-13T18:48:25Z",
      "expires_at": "2026-01-14T18:48:25Z",
      "session_token": null,
      "customer_email": null,
      "customer": {
        "name": "Felipe Castro",
        "email": "[email protected]",
        "metadata": {},
        "tax_id": {
          "type": "cl_rut",
          "value": "12088191"
        }
      },
      "payment_method_types": [
        "bank_transfer"
      ],
      "business_profile": {},
      "payment_resource": {},
      "setup_intent": "seti_3AUiBT4dia35S27G7mK8RnQg2SK"
    }
  }

Payment Method events

You will also receive a payment_method.activated with the info of the new saved payment method:

{
  "id": "pm_1NkL7QKs215JZ1LyW4c1m9Ut",
  "object": "payment_method",
  "card": null, 
  "created_at": "2021-10-15T15:22:11.474Z",
  "customer": "cus_NffrFeUfNV2Hib",
  "mode": "live",
  "metadata": {},
  "bank_transfer": {
    "account_holder_id": "123456789",
    "account_number": "9530516286",
    "account_type": "checking_account",
    "institution_id": "cl_banco_santander",
    "status": "active",
  },
  "type": "bank_transfer"
}

You should suscribe to all the following post-session events:

Create a payment session with a saved payment method (bank transfer)

If your customer has a bank_transfer saved payment_method , you can create a Checkout Session for a payment using it:

curl --request POST "https://api.fintoc.com/v2/checkout_sesison" \
  --header "Authorization: YOUR_SECRET_API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "amount": 100000,
    "currency": "CLP",
    "flow": "payment",
    "success_url": "https://merchant.com/success",
    "cancel_url": "https://merchant.com/cancel",
    "customer": "cus_123",
    "payment_method": "pm_1NkL7QKs215JZ1LyW4c1m9Ut",
    "payment_method_types": [
      "bank_transfer"
    ]
  }'

Test your integration (Sandbox available soon)

Using your test mode API Secret Key, you can create Checkout Sessions that simulate successful and failed outcomes without moving any money.

This lets you validate your full setup and payment flow end-to-end:

• Your backend API requests (creating sessions and handling responses)
• The redirect flow from your frontend to the redirect_url and back to the success_url or cancel_url after the setup or payment
• Webhook for post-session events to save customer, payment_method and payment result
  • After a successful setup o payment saving a payment_method, test creating a payment session using the saved method of the customer

To learn how to trigger specific scenarios, use the test credentials and special test values described in our testing guide.