PPRO
PPRO is a self-serve connector with one field — a webhook secret — and one property that should shape your rollout: it is forward-looking only, with no historical replay, so data starts on the day you turn the connection on. Connect it early: every day you wait is history you will not get back.
What you get
The payment lifecycle events PPRO sends for the local methods it processes for you: what was initiated, completed, failed or reversed.
Strongest for method coverage. It puts local payment methods into the same view as your card traffic, making honest method-mix comparison possible.
Weakest for cost and risk context. PPRO carries no fee or interchange data and no risk score or 3DS detail — it answers what happened to a payment, not what it cost.
Before you start
You need the Webhook Secret PPRO uses to sign deliveries, which lets Athia verify each delivery genuinely came from PPRO. Treat it as a credential, not a configuration value.
What matters is timing: the go-live timestamp is the effective start of your PPRO history.
Credentials Athia asks for
| Field | Required | What it is / where to find it |
|---|---|---|
| Name | Yes | Your label for this connection |
| Webhook Secret | Yes | The signing secret for PPRO event delivery — generate this in the PPRO console |
There is no Schedule field on this connector, and no historical time-frame option.
Setting up the connection
- Retrieve the Webhook Secret from the PPRO console.
- In Settings → Connections, choose + Add Connection and select PPRO.
- On Configure Connector, enter a Name.
- On Enter Credentials, paste the Webhook Secret.
- Choose Verify Connection.
- Copy the Athia Webhook Destination URL shown in the wizard and register it as the delivery destination in the PPRO console.
- Confirm deliveries are enabled in the PPRO console.
The connection then shows as ACTIVE and starts accepting deliveries, so Last synced advances as traffic arrives rather than at the end of a backfill.
Sync cadence
There is no schedule to pick, and nothing is missing. PPRO data arrives as PPRO delivers it, which is why the wizard offers no Schedule field: there is no polling interval to tune. Expected delivery latency is not published — confirm it with your Athia team.
PPRO has no historical replay. Nothing that happened before the connection went live will ever arrive through it. Turn it on as early in the rollout as you can, and plan a file load for anything earlier.
Limits and things to know
- Webhook-only and forward-looking — no historical replay. Data accumulates from the moment the connection is live; nothing before go-live arrives here. For that history, use a file drop — see Integrating Athia.
- Operational reports are limited to 31-day windows — reconcile a month at a time.
- No fee or interchange data. Cost analysis needs your rates loaded separately; see Integrating Athia.
- No risk score or 3DS detail.
- Amounts are minor units — divide by 100. Athia handles this on ingest.
- Card data is minimized. Field-level detail on what Athia stores is in Athia Data Dictionary.
Troubleshooting
| What you see | Likely cause | What to do |
|---|---|---|
ACTIVE but no data appears | No qualifying activity yet, or a secret mismatch | Confirm live traffic, then re-enter the secret |
ACTIVE but no data ever arrives | The Athia Webhook Destination URL was never registered, or delivery is disabled at PPRO | Register the destination URL in the PPRO console and enable delivery |
| Deliveries stopped arriving | Secret rotated, or delivery disabled at PPRO | Update the secret; confirm delivery is enabled |
Related
- Athia Connectors — the full connector catalog
- Integrating Athia — file drops, warehouse shares and the other integration paths
- Athia Data Dictionary — field definitions
Updated 1 day ago