Payments

Recurly

Send invoice notifications to OrcLink by webhook. OrcLink checks each one with your webhook signing key, then reads the invoice from Recurly with your API key.

Built, not yet tested liveBuilt. Not yet tested against a live Recurly account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Dashboard > Integrations > Recurly: paste Subdomain, API key and webhook signing key (subdomain:api_key:signing_key), then Connect. It is stored encrypted and never shown again.

What OrcLink reads

Invoice notifications (checked with your webhook signing key), then the invoice itself read from Recurly with your API key.

What OrcLink writes back

Nothing.

Never stored

Raw email addresses and phone numbers: hashed (SHA-256) the moment they arrive.
The raw payload: only its SHA-256, for provenance.
Your credentials and webhook secrets in clear: they are stored encrypted (AES-256-GCM).

Known limits

A renewal is recorded but not sent to ad platforms: only the payer's first payment is.
A refund lowers the net value of the payment.