Finance integration guide
Adyen + UbiGrowth workflows
Adyen is an enterprise payments platform handling acquiring, authorization, and settlement across channels. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Adyen part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a finance workflow around Adyen with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Payment, Modification, Notification, Merchant Account, Payment Method, and Dispute. Adyen models the lifecycle as an original Payment plus Modifications (capture, refund, cancel), so the current state of a transaction is the sum of its modifications rather than a field to read.
Adyen is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Finance integrations carry a different risk profile from the rest of the stack. A duplicated CRM record is annoying; a duplicated payment, a double-posted invoice, or an unauthorized write into Adyen is a real financial and control problem.
That is why most finance teams end up doing the work manually. The available automation is fast but cannot demonstrate what it did, and a number without a traceable basis is unusable in a function where everything has to be defensible.
You're likely here because
- Recurring finance analysis is mostly export, match, and reformat
- Approval trails live in email rather than in a system
- AI answers cannot be traced back to a source anyone will accept
Record model
What a Adyen integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Adyen's.
Identity and matching
Adyen models the lifecycle as an original Payment plus Modifications (capture, refund, cancel), so the current state of a transaction is the sum of its modifications rather than a field to read.
Start here
Consume notification webhooks for one payment method and reconcile authorisation-to-capture gaps that are currently invisible.
What this will not do
It will not simplify local payment methods. Each method carries its own flow and settlement timing; a single generic model will misreport some of them.
The constraint to plan around
Notifications are the authoritative channel and must be acknowledged; unacknowledged notifications are retried and, if never accepted, the state you hold silently diverges from Adyen's.
Build notes
What you actually have to reason about in Adyen.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| pspReference | the transaction handle, with modifications referencing the original |
| modification type | capture, refund, cancel — current state is the sum of modifications, not a field |
| eventCode / success | notification semantics, where success false is a real outcome rather than an error |
| merchantReference | your own key, and the only reliable reconciliation join |
| paymentMethod | local methods carry different flows and settlement timing |
Authentication
API key or Basic auth per merchant account, with separate test and live endpoints on account-specific URLs. Roles on the API credential govern which endpoints are reachable.
Events and delivery
Notifications are the authoritative channel and must be explicitly accepted; unaccepted notifications are retried and, if never acknowledged, your state diverges from Adyen's permanently.
Workflow
How the Adyen workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the source records
Connected Adyen records replace the recurring export step, so the analysis starts from current data.
Step 02
Match and reconcile
Records are matched against the other systems involved, and anything that does not match becomes an explicit exception rather than a silent adjustment.
Step 03
Present the working queue
Exceptions and items needing attention are presented with owners, so the review is a queue rather than a highlighted spreadsheet.
Step 04
Stage the action for approval
Where an action is required, it is prepared with its supporting records and held for explicit human authorization.
Design decisions
The finance decisions this connection forces.
Each of these has to be settled before the Adyen workflow is allowed to write anything.
Step 01
Start read-only and stay there longer than feels necessary
Read access to Adyen delivers most of the reporting and reconciliation value with none of the write risk. Add write paths only when a specific, bounded workflow requires them.
Step 02
Keep authorization human
Anything that moves money, changes billing state, or affects a closed period requires an explicit human authorization step that is recorded, not inferred.
Implementation path
How to implement the Adyen workflow.
- 01
Define the data boundary: which Adyen records the workflow may read, and what is explicitly out of scope.
- 02
Start with a reporting or reconciliation workflow you already produce manually, so the output can be checked against a known-good answer.
- 03
Reconcile the connected output against the last two closed periods before anyone relies on it.
- 04
After authorisation-to-capture reconciliation works, extend to settlement so the finance view closes the loop from payment to bank.
Governance
Controls that matter.
Control 01
Payment, billing, and period-affecting actions require explicit human authorization; automation prepares, people approve.
Control 02
Credentials are least-privilege and reviewed, with read and write scopes separated wherever the platform allows it.
Control 03
Every automated action leaves a record that can be reconciled against the source system.
Failure modes
How a Adyen integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Local state diverges from Adyen permanently.
Cause
Notifications were never acknowledged, so retries stopped without the state being accepted.
Fix
Return the expected acceptance response and treat notification handling as the source of truth.
Symptom 02
A capture appears successful and never settles.
Cause
Modifications are asynchronous and the synchronous response is only an acknowledgement.
Fix
Wait for the notification confirming the modification rather than trusting the API response.
Symptom 03
Reporting misstates certain payment methods.
Cause
Local methods have different flows and settlement timing than cards.
Fix
Model per payment method rather than through one generic abstraction.
What changes at scale
Notification volume scales with transaction count, and each requires acknowledgement. Process asynchronously but acknowledge synchronously, or the retry queue grows.
Examples
What a working Adyen workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Payment workflows
With Adyen connected read-only, the recurring view is assembled from live records rather than a fresh set of exports each cycle.
Reconciliation exception queue
Unmatched or unexpected items from Adyen become a working queue with owners, instead of highlighted rows in a spreadsheet emailed around the team.
Limitations and considerations
What to validate before you depend on this.
- Notifications are the authoritative channel and must be acknowledged; unacknowledged notifications are retried and, if never accepted, the state you hold silently diverges from Adyen's.
- Captures and refunds move money and are asynchronous — the API accepting a modification is not the modification succeeding. Treating the synchronous response as final produces reconciliation gaps.
- When a single generic payment model is wanted. Local payment methods differ enough that one abstraction will misreport several of them.
- Nothing produced here is accounting, tax, or audit advice, and no output should be treated as a professional opinion.
- Write access to Adyen carries real financial risk. Duplicate protection, idempotency, and an approval step are requirements rather than refinements.
FAQ
Adyen integration questions.
What records does a Adyen integration actually work with?
The primary records are Payment, Modification, Notification, Merchant Account, Payment Method, and Dispute. Adyen models the lifecycle as an original Payment plus Modifications (capture, refund, cancel), so the current state of a transaction is the sum of its modifications rather than a field to read.
What should the first Adyen workflow be?
Consume notification webhooks for one payment method and reconcile authorisation-to-capture gaps that are currently invisible.
What will a Adyen integration not do?
It will not simplify local payment methods. Each method carries its own flow and settlement timing; a single generic model will misreport some of them.
What is the main constraint to plan around?
Notifications are the authoritative channel and must be acknowledged; unacknowledged notifications are retried and, if never accepted, the state you hold silently diverges from Adyen's.
What changes about a Adyen integration at scale?
Notification volume scales with transaction count, and each requires acknowledgement. Process asynchronously but acknowledge synchronously, or the retry queue grows.
How does authentication work for Adyen?
API key or Basic auth per merchant account, with separate test and live endpoints on account-specific URLs. Roles on the API credential govern which endpoints are reachable.
Does Adyen support webhooks, and can they be trusted?
Notifications are the authoritative channel and must be explicitly accepted; unaccepted notifications are retried and, if never acknowledged, your state diverges from Adyen's permanently.
What is the risk of writing to Adyen?
Captures and refunds move money and are asynchronous — the API accepting a modification is not the modification succeeding. Treating the synchronous response as final produces reconciliation gaps.
When is connecting Adyen the wrong call?
When a single generic payment model is wanted. Local payment methods differ enough that one abstraction will misreport several of them.
What should a Adyen integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Adyen to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow write into Adyen?
Only where a specific bounded workflow requires it, with duplicate protection and an explicit human approval step. Most of the value is available read-only.
Is the output auditable?
Execution state and results return to the product surface, and analysis is grounded in connected records rather than an uploaded file, so an answer can be checked against its source.
Is this a replacement for the accounting system?
No. Adyen stays authoritative. The workflow layer sits around it to remove the export, match, and reformat cycle.
How this access is governed
What ARIA is allowed to do in Adyen, and who decides.
Connecting Adyen is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.