Introduction to Adfin Express

Core resources

Resource	What it represents	Typical operations
Customer	A customer record with contact details, mandate status, and information on the entity. Can be synced with accounting platform.	Create / update / list / delete customers (/customers endpoints).
Invoice	Distributed to a customer. Includes line items, taxes, due dates, and a unique invoice number.	Draft, activate, void, mark-as-paid, or bulk list via /invoices and /invoices/[id].
Direct-Debit Mandate	Used to request and hold consent to pull funds from the customer’s bank.	Create or cancel mandates per customer (/customers/[id]/directdebitmandates).
Webhook	Outbound events that keep your system in sync (e.g., invoice paid).	Configure per application

Create a customer
1. POST /customers with name, email, and contact information.
2. Collect and record a mandate URL; Adfin hosts the signature flow and updates the mandate status automatically.
Issue an invoice
1. Create or sync an invoice via POST /invoices.
2. Keep it in DRAFT until all details are final; update in place with PUT /invoices/[id].
3. Call :activate to distribute and (optionally) trigger Direct Debit collection.
Collect payment
1. Adfin schedules the Direct Debit or generates a hosted payment page for card/open-banking.
2. Track status transitions (SCHEDULED → SUBMITTED → PAID) on the invoice or payment request.
Reconcile & settlement
1. When funds are reconciled and settled via Adfin, you will receive webhooks for the events.
2. Webhooks deliver near-real-time events for invoice and customer updates
3. Remember, customers will also be using Adfin and Accounting software, so you should listen to events to update customers and invoices from Adfin to keep your system in sync.