Payment & Financial Systems

Payment Processing Fundamentals

Payment processing in food delivery involves multiple parties—customers, platforms, restaurants, drivers, and payment processors—with money flowing between them in complex patterns. The WIA-IND-009 standard specifies payment workflows, data formats, and integration patterns that ensure secure, reliable, and transparent financial transactions.

A typical transaction involves customer payment authorization at order placement, platform capture at delivery confirmation, distribution to restaurant (minus commission), driver payment, and eventual settlement to bank accounts. Each step must be secure, auditable, and compliant with financial regulations across different jurisdictions.

Payment Gateway Integration

Payment gateways like Stripe, PayPal, Square, and Braintree handle the technical complexity of card processing, fraud detection, PCI compliance, and settlement. The WIA-IND-009 standard provides abstraction layers that enable platforms to integrate multiple payment providers and switch between them without restructuring core application code.

Key integration points include payment method tokenization (storing reusable customer payment credentials securely), authorization and capture (two-step charging process), refunds and reversals, dispute handling, and compliance reporting. The standard's gateway-agnostic APIs enable platforms to offer customers choice of payment providers while maintaining consistent internal workflows.

Choosing the right payment gateway involves evaluating transaction fees, settlement speed, geographic coverage, feature set, integration complexity, and reliability. Many platforms integrate multiple gateways to offer regional payment methods, provide redundancy, or enable competitive pricing through volume negotiations.

Multi-Party Payment Splitting

Food delivery transactions must be split among multiple recipients. From a $30 order, perhaps $20 goes to the restaurant, $4 is platform commission, $4 is delivery fee for the driver, and $2 is platform operating revenue. Some platforms handle this through marketplace/marketplace facilitator models where they receive the full payment and then pay out to parties, while others use payment provider features for direct splitting.

Tip Handling

Tips represent a significant portion of driver earnings. The WIA-IND-009 standard requires complete transparency in tip handling—tips must be passed to drivers in full without platform deductions, and tip amounts must be clearly displayed to drivers before they accept orders. Customers should be able to add or modify tips before and after delivery, with changes reflected in driver earnings promptly.

Some jurisdictions regulate tip handling specifically, requiring that tips be paid to workers within certain timeframes or that tip pooling follow specific rules. The standard's configurable tip workflows accommodate these varying requirements while maintaining driver fairness.

Refunds and Dispute Resolution

When orders are cancelled, undelivered, or unsatisfactory, refunds must be processed fairly and quickly. The WIA-IND-009 standard defines refund workflows for various scenarios including customer-initiated cancellations before preparation, restaurant cancellations, delivery failures, and quality complaints. Each scenario has different fairness implications for who bears the cost.

Dispute resolution mechanisms handle situations where customers and restaurants disagree about whether a refund is warranted. Platforms typically mediate these disputes using evidence like delivery photos, GPS data, and order history. The standard specifies data collection and presentation patterns that enable fair dispute resolution while protecting privacy.

Financial Reconciliation

Restaurants, drivers, and platforms need to reconcile their earnings against actual bank deposits. The WIA-IND-009 standard provides detailed financial reporting APIs that break down earnings by order, fee type, and time period. Reconciliation reports should match bank deposits exactly, with clear explanations for any adjustments, holds, or fees.

Automated reconciliation systems can match platform reports against bank statements and flag discrepancies for investigation. This reduces accounting workload and enables faster detection of payment processing issues. The standard's structured reporting formats facilitate automated reconciliation tool development.

Payout Scheduling and Methods

Different stakeholders have different payout timing preferences. Restaurants typically prefer weekly or bi-weekly payouts for cash flow predictability, while drivers often want daily or instant payouts for immediate access to earnings. The WIA-IND-009 standard supports flexible payout scheduling and multiple payout methods including bank transfer, debit card transfer, digital wallets, and platform balance.

Instant payout features (enabling drivers to cash out earnings immediately) have become popular but require platforms to front cash before receiving settlement from payment processors. This creates liquidity requirements and potential fraud risks that must be managed carefully through daily limits, fee structures, and fraud monitoring.

Tax Reporting and Compliance

Platforms have tax reporting obligations to governments and may need to collect and remit sales tax, withhold income tax, issue tax forms to restaurants and drivers, and report large cash transactions. Tax requirements vary dramatically by jurisdiction, creating compliance complexity for platforms operating globally.

The WIA-IND-009 standard includes tax reporting data schemas and workflows that accommodate various tax regimes. Platforms should collect necessary tax information during onboarding (like TIN/EIN for US entities), calculate and collect applicable taxes on transactions, and generate required tax forms and reports. Integration with tax software services can automate much of this compliance burden.

Fraud Prevention

Payment fraud is a persistent challenge. Common fraud patterns include stolen credit card usage, friendly fraud (customers claiming they didn't receive orders they actually received), account takeovers, promo code abuse, and refund fraud. The WIA-IND-009 standard recommends multi-layered fraud prevention including transaction risk scoring, behavioral analysis, delivery verification, velocity checks, and customer reputation systems.

Machine learning fraud detection models learn from historical fraud patterns and flag suspicious transactions for review or blocking. However, overly aggressive fraud prevention creates false positives that frustrate legitimate customers. The standard emphasizes balanced approaches that protect against fraud while minimizing customer friction.

Currency and International Payments

Platforms operating internationally must handle multiple currencies, exchange rates, cross-border payment regulations, and varied payment methods popular in different regions. The WIA-IND-009 standard supports multi-currency operations through currency-aware data types, exchange rate management, and localized payment method integration.

Cross-border payments (e.g., a platform headquartered in one country paying restaurants in another) face additional complexity including correspondent banking fees, regulatory reporting, and longer settlement times. Platforms must communicate these realities clearly to stakeholders and potentially absorb costs to maintain competitive payout terms.