Platform Architecture & Operational Concepts

Learn how Digintu Pay automates corporate payment execution, invoice digitization, and bank ledger reconciliation.

Core Architecture: Converters vs. Pipelines

A fundamental operational distinction exists between format Converters and automated Pipelines.

  • Converters: Rules that define data transformations (e.g., mapping CSV to ISO 20022 pain.001 or camt.053 to an Excel sheet). They are executed on-demand in browser memory.
  • Pipelines: Continuous automated processing routes that combine an inbound ingestion channel, a converter rule, and an outbound destination.
  • Separation of Concerns: Build your transformation logic in Converters once, test it using living fixtures, and then deploy it into an automated headless Pipeline.

Zero-Retention Processing Model

Digintu Pay acts strictly as a transient data conversion middleware.

  • Volatile Memory Processing: Uploaded files and payment instructions are parsed entirely in volatile container RAM.
  • Immediate Discard: Once transformed and delivered to the target bank SFTP or webhook, raw payloads are purged instantly.
  • Audit Non-Repudiation: Diagnostic logs capture solely metadata (filename, timestamp, status code, SHA-256 hash), preserving zero financial records in permanent databases.

Workspace & Organization Setup

Configure corporate identity, debtor bank account defaults, and ordering party settings.

Setting Default Company Details

Establish fallback ordering debtor accounts and address information.

  • Navigate to Profile or open a Converter rule in the Mapping Canvas.
  • Click Tab 2 (Configuration & Defaults) and locate 'Sender Details & Address (Debtor)'.
  • Fill in your default Ordering Account (IBAN) and Bank BIC/SWIFT code.
  • Enter your company's structured street, building number, postal code, city, and ISO-2 country code.
  • Save changes. These defaults automatically populate ISO Group Headers whenever an input file omits explicit debtor metadata.

Managing Multiple Workspaces

Seamlessly operate across subsidiaries or accounting client mandates.

  • Workspace isolation ensures pipelines, custom schemas, and audit logs remain strictly segregated.
  • Owners can rename active workspaces directly from the Team Management page.
  • Team members invited to multiple organizations can accept guest invitations without creating duplicate login credentials.

Template Catalog & Pre-Built Schemas

Access verified clearing templates for European and Swiss payment networks.

Browsing & Activating a Template

Select tested configurations from the verified library.

  • Click the 'Catalog' button located on the top right of the Converters dashboard.
  • Use the search bar to filter by ERP provider (e.g., Bexio, Abacus, Dynamics), clearing format, or bank.
  • Click on any template card to inspect its pre-configured mappings, delimiters, and living test fixtures.
  • The canvas opens automatically with the template preloaded. Rename the rule and click 'Save Converter Rule' to add it to your workspace.

Custom Mapping Canvas

Build custom data mappings to convert bespoke ERP flat files, CSVs, or JSON payloads into ISO 20022 schemas.

1. Defining Formats & Delimiters

Step-by-step guidance on setting up source files.

  • Click 'New Converter' on the Converters page or choose 'Create from Scratch'.
  • Enter a descriptive rule name (e.g., 'Weekly Supplier Run - Dynamics NAV').
  • Select the Financial Domain: Accounts Payable (Vendor Payments), Bank Reconciliation (Statements), or Accounts Receivable (Invoicing).
  • Select your source input format (CSV, Excel, JSON, PDF) and desired target ISO schema (e.g., Swiss pain.001.09, EPC SEPA).
  • If tabular, specify column delimiters (comma, semicolon, pipe) and indicate whether row 1 contains headers.

2. Attribute Extraction & Field Linking

Auto-discovering columns and binding them to payment tags.

  • In the left sidebar, locate 'Sample Inbound Data'. Click 'Drag & Drop sample' and upload an example spreadsheet or JSON payload.
  • Click 'Extract Attributes'. The engine discovers all headers and renders a preview table.
  • Navigate to Tab 3 (Data Mapping Details) and expand the functional groups (Amounts, Beneficiary Bank, Remittance).
  • For each target ISO field, select the corresponding source column from the dropdown menu.
  • For missing fields, provide a static default value in the Fallback field.

3. Transformation Modifiers & Rules

Applying inline sanitization, currency formatters, and date parsers.

  • Click the transformation dropdown next to any mapped field.
  • Select modifiers: 'Trim Whitespace', 'Force Uppercase', 'Parse Decimal (1,000.50 -> 1000.50)', or 'Parse Date'.
  • For address blocks, apply 'Smart Split Address (Nov 2026)' to automatically divide strings into street, building, and town.
  • Multiple transformations execute sequentially from left to right.

In-Memory Simulation (Dry Runs)

Simulate conversions in real-time, inspect XML output, and ensure zero schema rejections before live bank submission.

Executing a Dry Run Test

Testing mappings directly within browser memory.

  • Open any converter rule and click 'Test Run (Dry Run)' on the footer, or click 'Run Tool' from the Converter card.
  • In the dialog, click 'Load Example Data' to populate the test fixture automatically, or drag a test file onto the dropzone.
  • Click 'Run Transformation Test'.
  • The engine parses the payload in volatile RAM and presents the syntax-highlighted output XML/JSON.
  • Review instruction totals and currency codes, or click 'Download File' to inspect the physical package.

Live Dispatch Mode vs Simulation

The consequences of activating the Live Dispatch toggle.

  • When simulating from an automated Pipeline, a 'Live Dispatch Mode' toggle appears.
  • Unchecked (Default): The execution generates the output strictly for browser preview. No external networks are contacted.
  • Checked: The generated file is physically transmitted to the configured outbound endpoint (external bank SFTP, webhook API). Use with caution on production routes.

Creating an Automated Pipeline

Automate straight-through processing routes with scheduled or event-driven workers.

Wizard Walkthrough

Creating a complete automated pipeline from scratch.

  • Navigate to 'Pipelines' in the main menu and click 'Create New Pipeline'.
  • Step 1 (Details): Assign a route name, toggle duplicate file verification (SHA-256), and configure email notification recipients.
  • Step 2 (Inbound): Choose how data enters (Provisioned REST API, Dedicated SFTP, Google Drive, or Email Inbox).
  • Step 3 (Converter): Link the pre-built mapping rule responsible for transforming the ingested files.
  • Step 4 (Outbound): Select where transformed ISO 20022 files are delivered (Bank SFTP, External Webhook, Digintu SFTP Drop, or Email).
  • Click 'Deploy Pipeline'. Your credentials and endpoints will generate instantly.

Inbound Channels (API, SFTP, Drive, Email)

Detailed connection specifications for all supported source ingestion protocols.

Provisioned REST API Ingestion

Direct HTTP POST specifications.

  • Target Endpoint: Post multipart/form-data or raw payloads to https://api-pay-dev-1.digintu.ch/api/v1/pipelines/execute/api.
  • Header Authentication: Provide your generated channel key via the X-API-Key header.
  • Response: Returns HTTP 200 with delivery metadata upon successful parsing, or HTTP 400 with diagnostic error details.

Provisioned SFTP Drop Folders

Connecting ERP background file exports via SFTP.

  • Server: Connect to ftps-pay.digintu.ch on port 2222.
  • Authentication: Use the provisioned username and secret password, or upload your corporate SSH public key for passwordless login.
  • Directory: Deposit files into the root /uploads folder. The background worker polls for complete file writes and processes them immediately.

Google Drive & Email Ingestion

Automated folder watching and inbox polling.

  • Google Drive: Provide an authorized corporate Google account email. Digintu provisions an encrypted shared folder and listens for new uploads.
  • Email Inbox: Forward accounting attachments to the unique assigned ingest address (e.g., pay-in+key@digintu.tech). Attachments are parsed and verified instantly.

Outbound Delivery & Webhooks

Transmit validated ISO 20022 messages directly to bank host-to-host systems or treasury endpoints.

Configuring External Webhooks

Streaming converted JSON/XML to upstream endpoints.

  • In the Pipeline wizard (Step 4), choose 'User API'.
  • Provide the target destination URL (e.g., https://erp.company.com/webhooks/payments).
  • Enter custom Authorization headers (Bearer tokens, API keys) or custom metadata headers.
  • Enable HMAC signing if your receiving server requires cryptographic payload verification.

External Bank SFTP Transmission

Delivering payment instructions directly to bank servers.

  • Select 'External SFTP' as the outbound destination.
  • Enter the bank's hostname, port (typically 22), username, and destination folder path (e.g., /clearing/inbound/).
  • Choose Logon Type: Normal (Password) or Key (Paste your bank-authorized SSH Private Key).
  • Transformed files are streamed directly to the bank host-to-host gateway upon pipeline completion.

HMAC, IP Whitelisting & SSH Keys

Harden endpoints against unauthorized requests, replay attacks, and network intrusion.

Configuring IP Whitelists (CIDR)

Restricting ingress to designated corporate static IPs.

  • Open your pipeline settings and navigate to Inbound Security.
  • Enter your company's egress public IP addresses in CIDR format (e.g., 195.141.22.0/24, 84.115.10.4).
  • Save changes. Connection attempts originating from non-whitelisted addresses are rejected at the edge with HTTP 403 Forbidden.

HMAC-SHA256 Payload Signing

Cryptographic message integrity verification.

  • Inbound Verification: Require incoming webhooks to pass an HMAC signature computed using your channel secret.
  • Outbound Signing: Digintu signs outbound HTTP payloads and attaches the digest in the configured header (default: X-Signature).
  • Payload tampering in transit will invalidate the signature, causing the receiving gateway to reject the transmission safely.

November 2026 Structured Addresses

Prepare for the mandatory Swiss SIX and European EPC structured address deadline.

Mandate Overview: Unstructured Address Rejection

Why legacy 7-line address blocks will fail clearing.

  • Regulatory Mandate: European and Swiss clearing networks mandate the complete elimination of unstructured address elements (AdrLine) by November 2026.
  • Non-Compliant Penalties: Payment instructions featuring unstructured addresses will be rejected automatically by bank clearing processors.
  • Requirement: All creditor and debtor addresses must be decomposed into Street Name (StrtNm), Building Number (BldgNb), Postal Code (PstCd), Town Name (TwnNm), and Country (Ctry).

Automatic Address Splitting Engine

How Digintu Pay sanitizes and parses address fields.

  • In your Converter Mapping Canvas, map your source full address string to rawUnstructuredAddress.
  • Apply the modifier: 'Smart Split Address (Nov 2026)'.
  • The engine parses street prefixes, house numbers, building suffixes, and postal codes across European formats.
  • The compiled ISO 20022 pain.001 file outputs clean, fully structured XML tags matching official validation schemas.

CAMT.053 Statement Reconciliation

Parse end-of-day bank balance statements and export clean CSV/Excel feeds for ledger reconciliation.

Parsing CAMT.053 Entries

Extracting opening balances, closing balances, and entry lines.

  • Drop your bank's CAMT.053 XML file into a conversion tool or automate ingestion via SFTP.
  • The parser extracts opening and closing book balances, entry value dates, credit/debit indicators (CRDT/DBIT), and transaction amounts.
  • Remittance descriptions and creditor references (SCOR / QRR) are normalized into clean tabular columns.
  • Download the result as a standardized Excel reconciliation workbook or route it directly into your cloud ledger.

Swiss QR-Bills & ZUGFeRD / Factur-X

Generate official Swiss QR payment slips and European Factur-X electronic invoices.

QR-Bill Generation Rules

Validating QR-IBANs and 27-digit structured reference numbers.

  • In the Converter Canvas, select the Invoicing domain with target format 'Client QR-Bill (PDF)'.
  • Enter your official Creditor Account (QR-IBAN starting with CH or LI).
  • If reference numbers are missing in source billing records, enable 'Auto-Generate Missing Payment References'.
  • The engine generates compliant, printable PDF payment parts featuring the Swiss cross and official QR code.

ZUGFeRD / Factur-X XML Profiles

Compiling EN16931-compliant hybrid invoice PDFs.

  • Select target format 'Client ZUGFeRD (PDF)' or 'Hybrid QR + ZUGFeRD'.
  • Choose your compliance profile: BASIC (standard B2B), EN16931 (EU government mandate), or EXTENDED.
  • The resulting PDF/A-3 document contains human-readable layout pages alongside embedded machine-readable XML.

Team Management & Roles (Owner vs Member)

Permissions model, guest access switching, and team invitations.

Role Permissions: OWNER vs MEMBER

Operational execution vs billing governance.

  • OWNER Role: Full administrative authority. Manages Stripe subscriptions, seat allocations, team invitations, credential rotation, and workspace deletion.
  • MEMBER Role: Operational authority. Can create and edit Converters, trigger manual pipeline runs, inspect audit logs, and download transformed files.
  • Security Boundary: Members cannot view sensitive API secrets, rotate SFTP passwords, or access billing portals.

Guest Workspace Switching

How team members seamlessly operate within invited client environments.

  • When an existing user accepts a team invitation to another workspace, they enter as an operational Guest Member.
  • Their own organization, subscription, and pipelines remain active in the background.
  • To return to their home environment at any time, users click 'Leave Workspace' in their Profile settings.

Billing, Capacity & Transaction Credits

Understanding transaction quotas, scaling add-ons, and subscription tiers.

How Credits Are Metered

Metered consumption per validated instruction.

  • Transactions: Each individual payment instruction in a pain.001 file or entry line in a bank statement consumes 1 Transaction Credit.
  • Free Tier: Includes 10 free credits every month. Ideal for ad-hoc testing and monthly small batch validation.
  • Standard Tier: Includes 250 transactions/mo, 1 active automated pipeline, and 1 user seat.
  • Advanced Tier: Includes 1,000 transactions/mo, 3 automated pipelines, and 3 team seats.

Scaling Capacity (Pipelines, Seats & Credit Packs)

Prorated upgrades via Stripe Billing.

  • Advanced plan owners can scale resources dynamically without changing tiers.
  • Navigate to Profile > Workspace Capacity > Manage Capacity.
  • Adjust counters for extra team seats (+EUR 9/mo), automated pipelines (+EUR 35/mo), or 100-transaction packs (+EUR 15/pack).
  • Prorated charges or credits apply automatically to your current billing cycle.

Audit Trails & Error Resolution

Inspect execution logs, verify cryptographic deduplication, and diagnose rejected transfers.

Reviewing Execution Audit Logs

Inspecting timestamps, processed record counts, and status codes.

  • On the Pipelines dashboard, click 'Actions' > 'View Audit Logs' next to any channel.
  • A chronological ledger displays all recent runs, original filenames, execution timestamps, and success/failure statuses.
  • Click on any log record to copy the original filename and view transaction counts or parsing warnings.

Duplicate Protection & Idempotency

How SHA-256 fingerprinting prevents double-payments.

  • If 'Allow Duplicate Files' is turned off in your pipeline settings, the system computes a SHA-256 hash of every incoming payload.
  • If an identical file is submitted within a 30-day window, the run aborts immediately with a duplicate collision alert.
  • This eliminates accidental double supplier payments caused by repeated ERP exports.