resource.event, and the event’s data field carries the affected resource.
For the envelope that wraps every event, see the Event object. To build an endpoint that receives events, follow the webhooks guide, which covers signature verification and the retry schedule.
Use the Product column to choose events for the product you are integrating. Some events apply to more than one product.
Which events to use for your product
Which events to use for your product
Business Accounts vs. PaymentsFor Business Accounts transfers, subscribe to
transfer.inbound.* or transfer.outbound.*. The checkout_session.*, payment_intent.*, and payout.* events belong to Payments. A Payout settles funds collected through Payments to your bank account; it does not represent an outbound Business Accounts transfer.Events shared by Direct Debit and PaymentsThe subscription_intent.* and charge.* events belong to Direct Debit. Payments also emits these events when enrolling bank accounts and processing charges through Chilean automatic bank debit (PAC). These events do not apply to card payments.For Payments subscriptions, follow the recurring payments guide for the checkout, payment method, and invoice events to handle.Invoice payment events
An invoice reachespaid in two ways, and the events differ. When Fintoc collects the invoice, you receive invoice.payment_succeeded and then invoice.paid. When you mark the invoice as paid because your customer paid you outside Fintoc, you receive invoice.paid alone.
Read external_payment in the payload to tell the two apart. The value is false when the money went through Fintoc and true when it did not.
Upcoming invoice previews
Fintoc sendsinvoice.upcoming ahead of each billing cycle so you can notify your customer before you charge them. Contact Fintoc to set how many days of notice you receive.
The payload previews an invoice that does not exist yet, so two fields behave differently from every other invoice.* event:
- The invoice carries no
id, because Fintoc has not created it. - The event’s
resource_idholds the subscription, not the invoice.
Entity onboarding payload
Theentity.onboarding.approved and entity.onboarding.rejected events carry the full Onboarding object, so you can read the reviewed step data in data, the uploaded documents, and the declared legal_representatives and shareholders without calling the API again. The payload omits submittable, because a reviewed onboarding can no longer be submitted.
For backward compatibility, the payload also keeps two fields that the Onboarding object does not have:
object_name: Alwaysonboarding_process.entity: A summary of theEntitywith itsid,holder_id,holder_name, andnationality.
type to tell the two kinds of onboarding apart. The keys inside data, and the slots in documents, depend on type and on the Entity’s country.
Account holder
An approvedaccount_holder onboarding lets the Entity own Account objects at Fintoc. The example shows an approved Mexican account_holder onboarding:
Onboarding object for every field in data, legal_representatives, shareholders, and documents.
Settlement recipient
Asettlement_recipient onboarding lets the Entity receive split payments. data.company_information.settlement_account holds the bank account where Fintoc pays the Entity’s share. A Chilean settlement_recipient onboarding opens no document slots, so documents and each legal representative’s documents are empty. The example shows an approved Chilean settlement_recipient onboarding for a company:
Entity that onboards as a natural person, Fintoc ignores legal_representatives, transactional_profile, and shareholders. The payload carries empty legal_representatives and shareholders arrays, and data holds only company_information.
Retry after a rejection
What you can do afterentity.onboarding.rejected depends on the onboarding type:
account_holder: You cannot retry through the API. AnEntityholds oneaccount_holderonboarding per mode, so creating another one returns409 Conflictwith the codeconflicted_request, even after a rejection. Contact Fintoc support to review the case. Fintoc can review a rejected onboarding again and approve it. You then receiveentity.onboarding.approvedwith the same onboardingid, so let your handler accept an approval that arrives after a rejection.settlement_recipient: Create a new onboarding for the sameEntitywith the corrected data. Arejectedorapprovedonboarding does not block a new one. While anothersettlement_recipientonboarding for theEntityis stillpending,in_progress, orsubmitted, creating a new one returns409 Conflict.