Payment Integrations

Logidav integrates with multiple payment providers to process card payments, buy-now-pay-later (BNPL) installments, and insurance-backed payment plans. Each provider has a dedicated API client that handles transactions and refunds.

Payment Flow

View diagram source

flowchart LR
    CUST[Customer] -->|Payment| PP[Payment Provider]
    PP -->|Transaction confirmation| LOGIDAV[Logidav]
    LOGIDAV -->|Refund request| PP
    PP -->|Refund confirmation| LOGIDAV
    LOGIDAV -->|Transaction log| DB[(Database)]

Diagram

Provider Overview

Provider	Type	API Client	Use Case
Stripe	Card payments	StripeApi	Primary card processor
Hipay	Card payments	HipayApi	Card transactions and refunds
Payline	Card payments	PaylineService	Card payments with full transaction logging
Klarna	BNPL	KlarnaApi	Buy-now-pay-later installments
Scalapay	BNPL	ScalapayApi	Buy-now-pay-later installments
Alma	BNPL	AlmaApi	Buy-now-pay-later plans
Alfy	Insurance / Payment	AlfyApi	Insurance-backed payment plans

Common Patterns

All payment integrations share these characteristics:

• API client in src/CoreBundle/Api/ handles communication with the provider
• Configuration is stored in parameters.yml (API keys, merchant IDs, endpoints)
• Transaction logging: payment events are recorded for auditing and reconciliation
• Refund flow: refunds are initiated from Logidav and confirmed by the provider

Payline transaction logging

Payline has the most detailed transaction logging via PaylineTransactionLogService. If you need a reference for building transaction audit trails, start with the Payline integration.

Error Handling

Scenario	Behavior
Payment declined	Status recorded; customer notified
Provider timeout	Retry with backoff; log the attempt
Refund failure	Alert raised; manual intervention required
Webhook delivery failure	Provider retries; Logidav processes idempotently