curl --request POST \
--url https://api.fintoc.com/v2/payment_intents \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"amount": 100000,
"currency": "CLP",
"payment_method": "pm_2bArifJWQ6CiZSofWxBNL1Hri2u",
"split": [
{
"entity_id": "ent_6Qd3kZvNxL8r",
"type": "flat",
"amount": 70000,
"charge_processing_fee": true
},
{
"entity_id": "ent_4Pq7sLwXy2Nc",
"type": "flat",
"amount": 30000
}
]
}
'{
"id": "pi_2cKoy3PEXAuvkr4ofXC1KdMvCgZ",
"object": "payment_intent",
"amount": 5000,
"business_profile": null,
"created_at": "2026-02-10T15:23:11Z",
"currency": "CLP",
"customer": null,
"customer_email": null,
"error_reason": null,
"expires_at": null,
"invoices": [],
"metadata": {
"order_id": "12345"
},
"mode": "live",
"next_action": null,
"payment_method": null,
"payment_type": "pac",
"payment_type_options": {},
"recipient_account": null,
"reference_id": null,
"sender_account": null,
"split": null,
"split_applied": null,
"status": "created",
"transaction_date": null,
"widget_token": null
}Create a payment intent
Creates a payment intent that charges a previously saved payment method, in the live or test mode of the API key used. Unlike POST /v1/payment_intents, which starts a customer-present flow completed through the Fintoc widget, this endpoint charges the payment_method directly, with no customer interaction and no widget token. This endpoint does not accept v1-only parameters such as recipient_account, customer_email, payment_type, or expires_at. The charge starts in the created status; Fintoc processes the charge asynchronously, so subscribe to webhooks to track the charge’s progress. Fintoc sends Mexican direct debit charges to the bank once per business day and receives the result on the following business day. Available for organizations on API version 2026-02-01 or later.
curl --request POST \
--url https://api.fintoc.com/v2/payment_intents \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"amount": 100000,
"currency": "CLP",
"payment_method": "pm_2bArifJWQ6CiZSofWxBNL1Hri2u",
"split": [
{
"entity_id": "ent_6Qd3kZvNxL8r",
"type": "flat",
"amount": 70000,
"charge_processing_fee": true
},
{
"entity_id": "ent_4Pq7sLwXy2Nc",
"type": "flat",
"amount": 30000
}
]
}
'{
"id": "pi_2cKoy3PEXAuvkr4ofXC1KdMvCgZ",
"object": "payment_intent",
"amount": 5000,
"business_profile": null,
"created_at": "2026-02-10T15:23:11Z",
"currency": "CLP",
"customer": null,
"customer_email": null,
"error_reason": null,
"expires_at": null,
"invoices": [],
"metadata": {
"order_id": "12345"
},
"mode": "live",
"next_action": null,
"payment_method": null,
"payment_type": "pac",
"payment_type_options": {},
"recipient_account": null,
"reference_id": null,
"sender_account": null,
"split": null,
"split_applied": null,
"status": "created",
"transaction_date": null,
"widget_token": null
}Body
Rules for dividing the payment between entities. Available for organizations with splits enabled. Provide 1 to 10 entries. All entries must use the same type, each entity_id can appear only once, and at least one entry must pay the processing fee. For flat splits, amounts must add up to amount. For percentage splits, amounts must add up to 10000 basis points (100%).
Show child attributes
Show child attributes
Response
Payment intent created. The charge starts in the created status; Fintoc processes the charge asynchronously.
Status of the payment intent. One of created (the charge was accepted and is awaiting processing), in_progress (Fintoc is processing the charge), succeeded (the charge completed), failed (the charge did not complete), rejected (the institution rejected the charge), expired (the payer did not act in time), or pending (the final status is not yet known). pending is only returned to organizations that have the pending status enabled.
created, failed, succeeded, rejected, in_progress, pending, expired "succeeded"
Was this page helpful?