Developer Docs

PagaFactu: Features ​

Invoice collection through Open Banking (PSD2), synchronous flow with collection URL and associated document.

PagaFactu is Zertiban's product for invoice collection through Open Banking (PSD2). It lets you generate a collection flow from an invoice and synchronously obtain the resources needed to execute it: the collection URL and the associated document in different formats.

It is designed to integrate directly with ERPs or invoicing systems, simplifying collection generation and the end-customer experience.

For the shared concepts of flows and operations, structure, states and transitions, see Flows and operations.

Integration options ​

PagaFactu offers three integration options depending on the level of control over collection generation and the end customer's document experience:

OptionDescription
Collection URL onlyOnly the link the end customer will use to complete the transfer is returned
URL + PDF with QR generated by ZertibanThe collection URL is returned together with a PDF automatically generated by Zertiban that includes the transfer details and a QR code linking to the collection URL
URL + PDF with appended pageThe client sends their own invoice as a PDF and Zertiban returns the collection URL together with the same document enriched by adding a single extra page at the end with the QR and link

PagaFactu features ​

FeatureDescription
Immediate collectionStandard SEPA transfers (D+1) or instant (SCT Inst, in seconds)
Scheduled collectionType FUTURE_PAYMENT with requestedExecutionDate (minimum 1 business day in advance)
PDF generation with QRBy setting generateDocument: true, Zertiban returns the PDF as base64 in the response
Enrichment via appended pageA single additional page is appended at the end of the client's document, including the collection QR and direct link
Expiration controlConfigurable between 1 and 156 days via expirationOffset
Operation cancellationPUT/flow/v1/operations/{operationUuid}/cancel available in CREATED or OPENED states (if no transactions are in progress)
Reconciliation via externalIdThe business identifier (e.g. invoice number) travels through the entire flow and webhook events

PagaFactu functional flow ​

1. ERP: Flow creation ​

The client's system makes a single synchronous API call:

POST /flow/v1/flows/pagafactu

This call sends:

  • invoice data,
  • amount,
  • debtor details,
  • and optionally the invoice PDF if using the appended-page document option.

Zertiban responds immediately with:

  • a ready-to-use collection URL,
  • the PDF with appended page (if applicable),
  • flow and operation identifiers.

2. ERP: Collection distribution ​

Zertiban does not send communications to the end customer. The ERP is responsible for delivering the collection link through whichever channels it considers appropriate:

  • Email
  • WhatsApp
  • SMS
  • Integration in the invoice or customer portal

At this point, the ERP can send directly either:

  • the collection URL, or
  • the document generated by Zertiban.

The appended page is the same in all cases, since it is generated only once at flow creation and is part of the returned document, including the QR and the collection link.

3. End customer: Accessing the flow ​

The end customer accesses the flow in two equivalent ways:

  • Opening the collection URL directly in their browser, or
  • Scanning the QR included on the document's appended page.

Either way they reach the same collection experience hosted by Zertiban. Once inside:

  • they select their bank,
  • they start the collection process,
  • the operation moves to the OPENED state.
CREATED → OPENED

4. Bank: Authentication and authorization (PSD2) ​

The customer is redirected to their online banking to complete Strong Customer Authentication (SCA). During this process they:

  • review the collection details,
  • authorize the transfer,
  • confirm the operation from their banking entity.

5. Zertiban: Collection confirmation ​

Once the bank confirms the operation, it transitions to the COMPLETED state and Zertiban emits the corresponding webhook:

json
{
  "eventType": "OPERATION_COMPLETED",
  "resource": {
    "externalId": "INV-2026-001",
    "status": "COMPLETED"
  }
}

6. ERP: Automatic reconciliation ​

The ERP receives the webhook and uses resource.externalId to:

  • locate the invoice,
  • mark it as collected,
  • run accounting or business processes.

Synchronous system behavior ​

Flow creation in PagaFactu is fully synchronous:

  • the collection URL is returned in the same API response,
  • the document with appended page (if applicable) is returned in the same response,
  • there are no asynchronous callbacks during the creation phase.

Delivery responsibility ​

Zertiban does not communicate with the end customer. The client's system is responsible for:

  • generating and distributing the collection link or document,
  • choosing the communication channel,
  • managing the notification experience.

Zertiban acts as the engine for collection flow generation and bank execution.

Next steps ​