SplatDev.Umbraco.Plugins.Payments.PagSeguro 2.2.1

Payments.PagSeguro

PagSeguro payment integration for Umbraco — create checkout sessions, track transactions, and manage payment status from a backoffice dashboard.

Compatibility

Installation

dotnet add package SplatDev.Umbraco.Plugins.Payments.PagSeguro

Quick Start

The plugin auto-registers via PagSeguroComposer, which sets up the EF Core DbContext, HttpClient, and IPagSeguroService.

Configuration

Add to appsettings.json:

{
  "PagSeguro": {
    "Email": "your-email@example.com",
    "Token": "your-api-token",
    "Sandbox": true
  },
  "ConnectionStrings": {
    "umbracoDbDSN": "Server=localhost;Database=umbraco;Trusted_Connection=True;"
  }
}

Set Sandbox: true for testing, false for production.

API Endpoints

Usage

// Create a transaction
const response = await fetch('/umbraco/api/pagseguro/CreateTransaction', {
    method: 'POST',
    body: JSON.stringify({
        reference: 'ORDER-001',
        amount: 99.90,
        description: 'Product purchase'
    }),
    headers: { 'Content-Type': 'application/json' }
});
const { paymentUrl } = await response.json();
window.location.href = paymentUrl;

Known Limitations

• No built-in checkout UI or front-end integration — API-only payment initiation
• The Token config value is never exposed to the frontend (only Email and Sandbox are returned by GetConfig)
• No webhook/IPN handling in the Umbraco plugin layer; depends on the parent SplatDev.Payments.PagSeguro library
• Lower-level API calls are delegated to the SplatDev.Payments.PagSeguro library

Changelog

2.2.1 — 2026-08-24

Package metadata only: the listing now carries an icon and search tags, and the project and repository links point at the organisation that actually hosts this code. No code changes.

2.2.0 — 2026-08-23

The Umbraco Marketplace listing now carries this plugin's screenshots. The listing keeps its own screenshot list rather than reading the README, and this one was empty — so the entry showed no images at all.

2.1.7 — 2026-08-22

• The dashboard renders. It threw while loading — Lit's css tag rejects an interpolated plain string, and the brand colours were interpolated as strings — so the custom element was never defined and the panel came up empty on every install.
• The status no longer claims a connection it has not made. It read "Conectado" whenever the plugin's own config endpoint answered, which it does with nothing configured at all, so an untouched install reported a live production connection. It now reports whether credentials are present: "Configurado" or "Não configurado".
• An install with no credentials says so up front, instead of letting the first transaction fail at PagSeguro.

2.1.6 — 2026-08-21

• A failed request now says so in the dashboard. Previously the dashboard kept its previous (usually empty) state, so a refused or failed call looked identical to having no data.

2.1.5 — 2026-08-21

• Dashboard now sends the backoffice token with its API calls. On Umbraco 17 those calls were arriving unauthenticated and coming back 401, which the dashboard rendered as an empty state rather than an error.
• A failed request now raises a notification instead of leaving the dashboard looking like there is simply no data.
• The plugin's tables are created on startup. They were never created before, so anything touching them failed on a fresh install.
• Runs on SQLite as well as SQL Server. It previously assumed SQL Server and failed with "Keyword not supported: 'cache'" on the database Umbraco's installer offers by default.

License

MIT © SplatDev