Introduction

Welcome to the PayGlobe Payment Gateway, your complete platform for payment management, dispute handling, and chargeback prevention.

Dashboard

The dashboard is your control center for monitoring all activities in your merchant account.

Overview

At the top you'll find summary statistics:

• Transactions Today - Total number of transactions for the day
• Volume Today - Total amount processed today
• Success Rate - Percentage of successfully completed transactions
• Open Disputes - Number of disputes awaiting response

Available Tabs

Transactions

View and manage all transactions processed by the gateway.

Available Filters

• Status - Filter by status (Completed, Failed, Refunded, etc.)
• Date - Date range
• Amount - Amount range
• Method - Card, PayPal, Voucher, etc.

Transaction Actions

Transaction Details (Eye View)

Clicking the icon opens the complete detail of a transaction, organized in four blocks:

• Transaction Information — Transaction ID, Description, Status, Payment Method, Payment Gateway, Total Amount and Card/Voucher amounts.
• Timestamps — Created and Updated.
• Timeline — chronological list of events, e.g. SYSTEM INITIATED (transaction created) → the gateway event (IGFS IGFS_000 / SALE, or a Bizum/Shift4/PayPal authorization) → SYSTEM COMPLETED. Some events are reconstructed from the transaction data when not explicitly logged.
• Payment leg details — gateway-specific data: for IGFS the Payment ID, operation type (SALE / PREAUTH / CAPTURE) and IGFS status; for Bizum the Redsys order, Ds_Response (0000 = authorized) and authorization code; for the other gateways the corresponding identifiers.

Disputes (Chargebacks)

The Disputes tab shows all chargebacks received from card networks and pre-dispute alerts.

Dispute Status

Responding to a Dispute

1. Click the icon to open the dispute details
2. Review the details: amount, reason, deadline
3. Upload evidence (receipts, shipping tracking, customer emails, etc.)
4. Write a response in the "Merchant Response" field
5. Click "Submit Response" before the deadline

Accepted Evidence Types

• RECEIPT - Receipt or invoice
• SHIPPING_PROOF - Proof of shipment (tracking)
• DELIVERY_CONFIRMATION - Delivery confirmation with signature
• CUSTOMER_COMMUNICATION - Emails or chats with the customer
• TERMS_OF_SERVICE - Terms of service/refund policy
• PRODUCT_DESCRIPTION - Description of the product sold

Pre-Dispute Alerts

Pre-dispute alerts allow you to prevent chargebacks by refunding BEFORE they become formal.

Alert Sources

Auto-Refund Engine

Configure the system to automatically refund alerts that meet certain criteria:

Risk Analytics

Monitor your dispute rate to avoid sanctions from card networks.

Card Network Thresholds

Monitored Metrics

• Current Dispute Rate - Dispute/transaction ratio for the current month
• Risk Level - LOW, MODERATE, HIGH, CRITICAL
• Win Rate - Percentage of disputes won
• Amount at Risk - Total amount in open disputes
• Prevention Rate - Effectiveness of the alert prevention system

Risk Levels

MO/TO — Telephone orders

Take a payment over the phone: the customer reads out the card details and your operator types them into the bank's page, inside your dashboard.

Before you can use it

The tab only appears once PayGlobe has switched it on, and that happens after you provide two things: the dedicated MO/TO terminal issued by your acquirer (a separate one, with 3D Secure disabled) and your PCI SAQ. The tab closes by itself the day the SAQ expires — renew it before that date.

Taking a payment

1. Open the MO/TO tab and enter amount, order reference and description
2. Click "Apri l'incasso": the bank's card page opens on the right
3. Type the card details your customer reads out, in that page
4. The result appears on its own — it comes from the bank, not from the page

Payment Links

Create shareable payment links via email, SMS, WhatsApp, or QR code.

Creating a Payment Link

1. Click "Create Payment Link" in the Payment Links tab
2. Enter amount, description, and customer data
3. Choose the mode: LINK (you share it), MAIL (we email it to the customer), or SMS (there is no SMS channel: you get the link and send it yourself)
4. Set the expiration (1-365 days)
5. Click "Create" and copy the link or QR code

A link carries one payment attempt: if the payment fails for good, create a new link.

The email your customer receives

With linkType=MAIL PayGlobe emails the link for you. The default message already says who is asking for the money, how much, what for, and until when the link is valid — but you can rewrite it: Email template, next to "Create New Link".

Two things worth knowing before you edit it:

• The body must keep {{link}} somewhere — without it the customer has nothing to open, so the save is refused.
• It is email HTML: tables and inline styles. Anything that runs (scripts, event handlers, javascript: links) is stripped when you save, and we tell you when that happens.

Common Uses

• Invoicing - Send invoices with payment link via email
• QR Code POS - Print QR codes for in-person payments
• Social Commerce - Share links on WhatsApp/Instagram
• Remote Sales - Accept payments without integrated checkout

Bank Account (AIS)

Monitor incoming bank transfers to your business bank account for automatic order matching and reconciliation.

Supported Banks

PayGlobe integrates with major European banks via PSD2 Open Banking APIs (Account Information Services - AIS):

How to Connect Your Bank Account

1. Click "Connect Bank Account" - In the Bank Account tab, click the green "Connect Bank Account" button to start the process
2. Select your bank - Choose your bank from the list of supported institutions
3. Authorize access via SCA - You will be redirected to your bank's website (e.g., Unicredit Online Banking) to log in and authorize PayGlobe to access your account information
4. Select accounts - Choose which bank accounts you want to monitor for incoming transfers
5. Confirm consent - Review and confirm the consent (valid for 90 days, then renewal required)

Automatic Polling

Once connected, the system automatically fetches new incoming transfers:

• Frequency - Up to 4 times per day (PSD2 regulatory limit)
• Schedule - Recommended: 8:00, 12:00, 16:00, 20:00
• Manual refresh - You can trigger a manual sync from the dashboard (counts toward daily limit)

Transfer Matching

The system tries to automatically match incoming transfers to your orders using:

• Payment Reference - Searches for order IDs/references in the transfer description (causale)
• Amount - Exact match of the expected payment amount
• Customer Name - Cross-reference with customer data when available
• Manual Matching - For unmatched transfers, you can manually link them to orders from the dashboard

Use Cases

Workflows

Automate actions based on payment events with the visual workflow builder.

Available Templates

• Personalize Orders - Send personalized emails after payment
• Dispute Response - Automatic notification when a dispute arrives
• Refund Processing - Workflow for refund approval

Available Triggers

API Keys

Manage API keys for programmatic integration.

Key Types

API Authentication

Authorization: Bearer sk_test_YourSecretKey

AI Agents

Let an AI assistant work on your account — read your takings, prepare payment links, issue refunds — with only the permissions you choose and a spending limit you set.

Why an agent gets its own key

You have one secret key, and your website and your systems already use it. If you gave it to an assistant, taking access away from the assistant would mean changing the key everything else depends on. So an agent gets a key of its own: revoking it changes nothing else.

Creating one

Open the AI Agents tab and choose New agent.

1. Name it for what it does — it is what you will read when you have several and need to remove one.
2. Say who runs it, if it is not you. An assistant run by an agency is not the same as one running on your own machine.
3. Tick only the permissions it needs. Reading is enough for most assistants. Permissions that move money are marked.
4. Set the limits if you granted refunds or captures. A maximum per operation is required; a daily maximum is worth setting too, or the per-operation limit can be worked around by repeating.
5. Choose when it expires. Up to 90 days, and shorter is better.

Creating or removing an agent requires your secret key, not the publishable one: it is an owner's decision, not a everyday dashboard action.

What an assistant can be allowed to do

Reading your transactions, totals, payment links, disputes and subscriptions. And, if you allow it, three things that touch money: create payment links, refund a payment, and retry a failed subscription renewal.

Anything that moves money needs a ceiling from you, and the assistant is told those ceilings when it connects — including how much of today's allowance is left. It knows before it tries.

Watching what it does

The clock icon next to an agent shows its recent calls: what it asked for, for how much, and whether it was allowed.

Refused calls are kept on purpose. An assistant can be talked into things — it reads order descriptions, emails and tickets written by other people, and that text can try to give it instructions. An agent repeatedly asking for permissions it does not have is the sign that something is pushing it. That is exactly what you want to see.

Removing access

Letting an agent do the reordering

An agent can charge a card your customer has already saved — a weekly refill, a standing order — but only in a shape you control. You write the order first, with the amount and what kind of thing it is; the agent can only confirm it. It never picks the figure itself.

On top of your usual ceilings you can then say what it may buy: an amount per purchase, an amount per day, how many purchases per day, and which categories at all. That last one matters more than it looks: ten reorders of three euros break no money limit and are still ten deliveries nobody asked for.

Revoking takes effect on the agent's next call. Nothing else on your account is touched. If an assistant starts behaving oddly, revoke first and work out why afterwards — you can always issue a new key in a few seconds.

Technical setup, including how to connect a tool such as Claude Desktop, is in the integration guide.

Webhooks

Receive real-time notifications when events occur in the gateway.

Configuration

1. Go to Settings > Webhook Configuration
2. Enter your Webhook URL (e.g.: https://yourserver.com/webhook)
3. Copy the automatically generated Webhook Secret
4. Implement signature verification in your backend

Signature Verification

Each webhook includes an X-PayGlobe-Signature header with HMAC-SHA256 signature:

// Node.js example
const crypto = require('crypto');

function verifyWebhook(payload, signature, secret) {
    const hmac = crypto.createHmac('sha256', secret);
    hmac.update(payload);
    return hmac.digest('base64') === signature;
}

Webhook Events

• payment.completed - Payment completed
• payment.failed - Payment failed
• refund.issued - Refund issued
• dispute.opened - New dispute
• dispute.resolved - Dispute resolved
• alert.received - Pre-dispute alert received

Payment Methods

Configure accepted payment methods.

Available Gateways

Recurring Payments (Subscriptions)

Charge your customers automatically on a recurring schedule — subscriptions, memberships, "Netflix-style" billing. It builds on Card Tokenization: the card is saved as a token on the first payment and reused for every following charge, with no buyer interaction.

Everything lives under the Subscriptions tab of the dashboard, which has four sub-tabs: Plans, Subscriptions, Dunning and Analytics.

The two building blocks

• A Plan is what you sell on a recurring basis: price, currency, interval (monthly, yearly…), optional trial, setup/cancellation fees, and any custom fields you want to collect. You define it once.
• A Subscription is one customer enrolled in one plan, with their saved card, status and next billing date.

Step 1 — Create a plan

1. Open the Subscriptions tab → sub-tab Plans → click + New Plan.
2. Fill in name, price, currency and interval (e.g. €9.99 every 1 MONTH).
3. Optionally set a trial (free days before the first charge), a setup fee or cancellation fee, and the duration (runs forever, a fixed number of cycles, or until a set date).
4. Optionally add custom fields to collect at signup (order number, VAT, cost center…). Mark one text field as primary to have it auto-fill the merchantReference on every webhook.
5. Save. The plan appears in the list with its own code.

Step 2 — Get customers subscribed

There are three ways a customer ends up with a saved card and an active subscription:

• Share link (most common) — click Share on a plan to get a subscribe URL (with QR code and a copy button). The customer opens it, fills email + name + card + any custom fields, and confirms. You can personalize the link with ?ref=YOUR_ORDER_ID (flows into merchantReference) and ?customer=email (pre-fills the form).
• New Subscription (server-side) — from the Subscriptions sub-tab, + New Subscription creates one and returns a checkout link to send the customer, for when you already have the order in hand.
• Import an existing card token — if the customer already paid once (or you tokenized at a POS), reuse that token instead of asking for the card again. The token must be MIT-eligible (allowed for merchant-initiated charges); a one-off token is rejected.

Step 3 — Automatic billing & dunning

1. At each cycle the gateway charges the saved token automatically (server-to-server, no buyer needed) and sends the standard webhook with the outcome.
2. If a charge fails, the subscription enters Past Due and the retry engine takes over, following your retry policy (how many attempts, how many days apart, and what to do when they run out: cancel, pause, or mark unpaid).
3. Optional dunning emails are sent before each retry, with a link for the customer to update their card.
4. Every automatic charge also shows up in Transactions like any other payment, with its own payment ID and webhook.

Managing a subscription

From the Subscriptions sub-tab, the eye icon opens the detail; the row actions let you:

• Pause / Resume — temporarily stop and later restart billing.
• Cancel — immediately, or at the end of the current paid cycle.
• Change plan — move the customer to another plan, choosing how to prorate the difference.
• Retry now — force an immediate charge attempt on a Past Due subscription.
• Update card — replace the saved payment method.

Status reference

IGFS Adapter

If you already integrate directly against IGFS (N&TS/Nexi PGW REST), you can move onto PayGlobe without changing any code. The IGFS Adapter speaks the native IGFS wire protocol — same paths, same txHead/txReq/txRes JSON, same HTTP-Signature, same IGFS_000 — and routes everything to PayGlobe behind the scenes.

You change three configuration values and nothing else:

The path stays /MONEYNET_CG_SERVICES on purpose: the HTTP-Signature covers (request-target), so changing the path would change the signed string and force a code change. Only the host moves.

Supported operations

• POST /pgw/payment/init
• GET /pgw/payment/verify (alias /verification)
• POST /pgw/payment/capture · /reversal · /refund

Tokenizer endpoints (/pgw/tokenizer/check, /pgw/tokenizer/delete) are coming soon. Not available yet: /pgw/payment/selector, pay-by-mail and checkout — calling one returns 404.

What you gain by moving

The buyer lands on the PayGlobe checkout, so your unchanged IGFS integration can accept methods IGFS does not have — Bizum, PayPal, Satispay, crypto, meal vouchers. Your client still sees a normal successful IGFS transaction.

Full details, signature recipe and migration steps: igfs-adapter.html. To get test credentials, contact support@payglobe.it.

2FA Authentication

Two-factor authentication protects access to the dashboard.

2FA Setup

1. On first login, you will be shown a QR code
2. Scan the QR code with Google Authenticator or similar app
3. Enter the 6-digit code generated by the app
4. From now on, you'll need to enter the TOTP code at each login

Transaction Status Codes

Glossary

ARN (Acquirer Reference Number)

Unique transaction identifier assigned by the acquirer. Used to track the transaction in banking systems.

Chargeback

Forced refund request by the cardholder through their bank. Costs approximately €15-25 in fees plus the disputed amount.

Dispute Rate

Ratio between number of disputes and number of transactions in a period. Networks impose limits (Visa 0.9%, MC 1.0%).

IGFS

Internet Gateway Financial Services - Payment gateway for card transactions.

Pre-Dispute Alert

Early notification of a potential dispute, before it becomes a formal chargeback. Allows for preventive refunding.

PSP (Payment Service Provider)

Payment service provider that processes transactions (e.g.: IGFS, PayPal, Stripe).

RDR (Rapid Dispute Resolution)

Visa program for rapid dispute resolution through automatic refund.

SCA (Strong Customer Authentication)

Strong customer authentication required by PSD2. Includes 3D Secure for online payments.

TOTP (Time-based One-Time Password)

Time-based one-time password, used for 2FA authentication.

Webhook

HTTP notification sent by the gateway to your server when an event occurs (payment, dispute, etc.).

Support