ProAbono Metadata in Stripe

Overview

A business collecting through Stripe holds the same transactions in two places: the ProAbono invoices and the Stripe payments that settle them. Every object created in Stripe by ProAbono carries metadata prefixed pa_ — pa_ for ProAbono — which ties it to the ProAbono objects behind it: invoice, customer, payment. That metadata is what makes operations traceable between the two platforms.

The traceability serves several purposes:

bank reconciliation: matching a Stripe payout with the ProAbono invoices it settles;
business intelligence (BI): combining Stripe and ProAbono data in the same analyses;
checks: verifying, for instance, that every Stripe payment ties back to a ProAbono invoice;
investigation: tracing a Stripe payment or customer back to its origin in ProAbono, to look into a bug or a situation reported by a customer.

How It Works

Metadata on a Stripe Customer

Metadata	Example	Description
`pa_customer_id`	`133700`	Unique internal identifier of the ProAbono customer. Technical use only.
`pa_customer_ref`	`cust-42`	Customer reference in ProAbono. Uniquely identifies the customer and is printed on the invoices sent to that customer.

Metadata on a Stripe Payment

Metadata	Example	Description
`pa_customer_id`	`133700`	Unique internal identifier of the ProAbono customer. Technical use only.
`pa_customer_ref`	`cust-42`	Customer reference in ProAbono, the same value as on the customer.
`pa_invoice_id`	`4577651`	Unique internal identifier of the ProAbono invoice, distinct from the invoice number printed on the document. It is enough to retrieve the invoice, number included, through the ProAbono API.
`pa_request_id`	`2487116`	Unique internal identifier of the payment request: the request sent to Stripe to collect this payment, also called a payment attempt. An attempt can succeed or fail, and each one carries its own identifier. Technical use only.

Two keys are worth keeping apart: pa_customer_ref is public — it appears on the customer’s invoices — while every identifier ending in _id is internal to ProAbono and appears nowhere on a document.

A Stripe customer carries two keys where a payment carries four: an invoice and a payment request only exist once a payment has been requested.

Bank Reconciliation

A payment operator does not transfer each transaction separately. Payments are collected, then paid out in an aggregated payout: one transfer bundling many transactions, which reaches the bank account as a single statement line with no breakdown. A payout contains payments, refunds and, depending on the operator, fees of its own, such as its commissions.

Matching a payout with the ProAbono invoices can start from either side.

On the Stripe side, the breakdown of the payout is read in the Stripe dashboard: the payments it bundles are listed, and each payment carries its ProAbono metadata. The number of each invoice is then obtained with a simple request to the ProAbono API, from pa_invoice_id; the reference read in pa_customer_ref can be searched as it stands in Subscribers. This route can be fully automated, since the Stripe API returns the same metadata in the metadata object of a payment or a customer.

On the ProAbono side, the reconciliation relies on the Automated Transactions list: each transaction appears with the customer reference, the invoice number and, in the last column, the transaction identifier at the payment operator — Stripe here. Like every ProAbono list, the Automated Transactions list can be exported as a CSV or JSON file, or extracted through the API BackOffice. Separate from the API Live, that API is meant above all for data extraction.

Payouts, on the other hand, are not visible in ProAbono: Stripe makes them directly to the business’s bank account. A full payout is therefore matched by joining two files — the list of its payments exported from Stripe, and the automated transactions — on the Stripe transaction identifier, rather than opening payments one by one.

Both routes can be automated through the APIs: see How to Automate Bank Reconciliation.