spayd-applied

User Guide - SPAYD Applied

Complete guide for using the SPAYD Applied suite of applications.

Table of Contents

  1. SPAYD QR Generator
  2. Batch Payment Processor
  3. FioFetch Transaction Manager

SPAYD QR Generator

Overview

The SPAYD QR Generator creates standard Czech QR payment codes that work with all Czech banking apps. Generate payment requests quickly by selecting accounts, events, and entering amounts.

Live Demo: https://pexmor.github.io/spayd-applied/

Getting Started

First-Time Setup

  1. Open the application in your web browser

  2. Add your bank account(s):

    • Click the hamburger menu (☰)
    • Select “Accounts”
    • Click “Add Account”
    • Enter account name and IBAN
    • Click “Save”
  3. Create payment events (optional):
    • Click “Events” in the menu
    • Click “Add Event”
    • Enter event name, select account, set default amount
    • Click “Save”

Main Features

1. Generate QR Payment

Main Screen - Generate Tab

Main screen

Steps:

  1. Select a bank account from dropdown
  2. Choose an event (optional) or leave as “Select Event”
  3. Enter the payment amount
  4. Enter Variable Symbol (VS) - auto-generated or manual
  5. Add a message (optional)
  6. Click “Generate QR Code”

Result:

QR displayed

2. Manage Accounts

Accounts Tab

Accounts

Actions:

Tips:

3. Manage Events

Events Tab

Events

Events are payment templates for recurring transactions.

Actions:

Use Cases:

4. View Payment History

History Tab

History

View all previously generated QR payments.

Features:

Actions:

5. Monitor Sync Queue

Sync Queue Tab

Sync queue

Monitor webhook sync status (if configured).

Status Types:

Actions:

6. Configure Settings

Global Configuration

Global config

Available Settings:

Import/Export Settings:

Language Support

Switch between Czech and English:

  1. Click language switcher (CS/EN) in top bar
  2. All UI text updates immediately
  3. Language preference saved

Offline Mode

The app works completely offline:

Data Storage:

Tips & Best Practices

  1. Organize with Events: Create events for common payments
  2. Use Descriptive Names: Makes selection easier
  3. Variable Symbols: Use unique VS for payment tracking
  4. Regular Backups: Export settings periodically
  5. Test QR Codes: Verify scanning before sharing

Troubleshooting

QR Code Won’t Scan:

Data Not Saving:

Sync Failing:

Batch Payment Processor

Overview

Generate multiple payment requests with email notifications. Perfect for event organizers, clubs, or businesses needing to invoice multiple people.

Access: https://pexmor.github.io/spayd-applied/app/batch.html

Getting Started

Workflow Overview

  1. Import or enter people data (name, email, amount, VS)
  2. Configure accounts and events
  3. Generate payment QRs for all people
  4. Generate email templates
  5. Export batch download (HTML emails + QR images)

Features

1. People Data Management

Import from Excel/CSV:

  1. Click “Import Data”
  2. Select Excel or CSV file
  3. Map columns: Name, Email, Amount, Variable Symbol
  4. Preview and confirm import

Required Columns:

Manual Entry:

  1. Click “Add Person”
  2. Fill in form fields
  3. Click “Save”

2. Account & Event Management

Similar to main app but uses separate storage.

Setup:

  1. Add bank accounts
  2. Create events for the batch
  3. Select event for batch processing

3. Generate Batch Payments

  1. Click “Generate All”
  2. System creates:
    • Individual QR codes for each person
    • HTML email templates
    • Text email alternatives
  3. Preview generated emails

4. Email Preview

Features:

Customization:

5. Export Batch

Export Package Includes:

Export Options:

Use Cases

  1. Event Invoicing: Send payment requests to attendees
  2. Club Memberships: Annual fee collection
  3. Group Expenses: Split bills for trips/events
  4. Small Business: Invoice multiple clients
  5. Educational: Collect course or workshop fees

Tips

  1. Prepare Data: Use Excel template for consistency
  2. Unique VS: Ensure Variable Symbols are unique for tracking
  3. Test First: Run test with 1-2 people before full batch
  4. Backup Data: Export people list before clearing
  5. Email Delivery: Use reputable email service for sending

FioFetch Transaction Manager

Overview

Fetch and manage transactions from Fio Bank API. View transaction history, configure automatic fetching, and export data.

Requires: Fio Bank API token (free from Fio Bank internet banking)

Getting Started

# Build and run
./d10_build.sh && ./d20_run.sh

# Access at http://localhost:3000

See DOCKER.md for complete guide.

Option 2: Local Development

Backend:

cd fio_fetch_py
uv sync
fiofetch --fio-token YOUR_TOKEN

Frontend:

cd fio_fetch_webui
yarn install
yarn dev

Features

1. Dashboard

Overview:

2. Transaction List

Features:

Columns:

3. Fetch Controls

Manual Fetch:

  1. Click “Fetch Now”
  2. Transactions downloaded from Fio API
  3. Stored in local database
  4. View in transaction list

Set History Limit:

Steps:

  1. Enter number of days (1-365)
  2. Click “Set History Limit”
  3. Confirmation message shown
  4. Next fetch will respect limit

4. Configuration

Required Settings:

Optional Settings:

Get Fio Token:

  1. Log in to Fio Bank internet banking
  2. Navigate to API settings
  3. Generate read-only token
  4. Copy and paste into FioFetch config

5. Data Export

Export Formats:

Export Steps:

  1. Go to Transaction List
  2. Apply filters if needed
  3. Click “Export”
  4. Select format
  5. Download file

Understanding History Limit (Zárazka)

What is it?

When to use:

How to set:

  1. Decide how far back to fetch (e.g., 30 days)
  2. Enter days in “Set History Limit”
  3. Click submit
  4. Run “Fetch Now”

Example:

API Rate Limits

Fio Bank Restrictions:

FioFetch Handling:

Troubleshooting

Cannot Fetch Transactions:

422 Error:

Connection Timeout:

No Transactions Shown:

Docker Specific

Container Management:

# View logs
./d40_logs.sh

# Stop container
./d30_stop.sh

# Restart
docker restart fiofetch

# Check status
docker ps | grep fiofetch

Data Location:

Backup:

# Backup data
cp -r ~/.config/fio_fetch ~/backups/fio_fetch-$(date +%Y%m%d)

Security Notes

  1. Protect Your Token: Keep Fio token secret
  2. Read-Only Token: Use read-only token (not write)
  3. Local Storage: Data stored locally only
  4. No Cloud Sync: Transactions stay on your machine
  5. HTTPS: Always use HTTPS for web UI

Advanced Usage

API Access:

WebSocket:

Custom Deployment:

Support & Resources

Documentation

Common Issues

See Troubleshooting sections above for each component.

Getting Help

  1. Check relevant documentation
  2. Review error messages carefully
  3. Test with demo data (FioFetch)
  4. Check GitHub issues

Reporting Issues

When reporting issues, include:

Happy payment processing! 💰

This site is open source. Improve this page.