Payments
Get paid, and have the books already know.
Taking a card is the easy part. The hard part is the Tuesday payout that covers forty charges, three refunds and a chargeback, and still has to reconcile to the cent. Both halves are here — and so is the other direction: paying your suppliers from the same books.
Rails that are actually wired
- Redsys
- Revolut
- Stripe
- PayPal
- Adyen
How the money arrives
Five ways to get paid, every one wired to the books.
Every name below is an integration that works today. Use the one your customers already pay with, and the money arrives already booked.
Cards, through your bank
The gateway most Spanish banks put in front of card payments. Your customer pays from a link or the portal, and the card can be kept on file for the next one — with the original authorisation referenced, the way the scheme requires.
Cards
The same checkout and the same saved-card behaviour, against a Revolut Business account rather than a bank gateway.
Cards and direct debit
Cards, plus the one thing the other rails do not do: charging a customer off-session. You onboard once, the mandate lives on your own connected account, and the money lands in your balance rather than passing through ours.
PayPal checkout
Your customer pays on PayPal’s own page, from a link or the portal, with their PayPal balance or a card. It can be kept on file for the next one. The money is yours the moment PayPal takes it — not on a payout schedule — and the fee is already known, so the books carry both the same day.
Good to know
Its balance is reconciled like one more bank account, and you can pay suppliers straight out of it.
Settlement reports
Payout reports are imported and reconciled like Stripe’s.
Good to know
Keep taking payments with Adyen as you do today; aicroo takes care of reconciling what it pays out.
Off-session
Invoices that collect themselves
With a mandate in place, an invoice can charge its own customer a few days after it is issued, retry on a schedule you set if it fails, and stop at a ceiling you set so nothing large ever moves without a person. It is the same mechanism aicroo uses to bill its own customers, pointed outward.
How the money leaves
Pay suppliers from the books, and still sign at the bank.
A payment run no longer ends in a file somebody uploads by hand: it goes to the bank itself, and the final yes is always yours — your signature at the bank, an approval in Revolut, or, for PayPal, a second person inside aicroo.
Payment runs, signed at your bank
The payment run goes to your own bank through Ponto as one instruction: the same transfers, references and date the SEPA file would carry, and the file is still kept beside it. You sign at the bank, with the bank’s own security, and the run follows the bank’s answer until the debit arrives.
Good to know
From any account connected through Ponto whose bank accepts payment initiation, with up to 1,000 transfers under a single signature.
Payment runs, approved in Revolut
The run becomes a payment draft in your Revolut Business account, one transfer per line. Someone on your team sends it from the Revolut app; aicroo follows each transfer, and each bill is settled off its own line in the Revolut feed.
Good to know
You give the final yes: aicroo reads the account and prepares the drafts, and the money moves when someone on your team sends them in Revolut.
A bill paid from your PayPal balance
Pay a supplier who works through PayPal from the balance your own PayPal sales built up — one bill, or several asked for together. The payment and PayPal’s fee are booked when PayPal confirms it, and a payout the supplier has not claimed is flagged before PayPal sends the money back.
Good to know
Four eyes inside aicroo: one person asks, a different person approves, always within a daily limit you set. Approvals come from people, never from an API key.
SEPA payment runs
Put approved supplier bills in one run — or the month’s payroll, or the expense reimbursements — and take the SEPA file any bank accepts. When the debit reaches the statement the run settles itself, bill by bill, and a transfer the bank returns puts its bill back to pay.
Where your customer stands
Two portals, with payment already inside them.
A payment rail with nowhere for the customer to stand is an API key in a drawer. Both portals are part of the product — not an add-on, not a separate price, and not something you build.
The customer portal
Watched by Collections
Your customer opens a link from their inbox — no account, no password, a code to prove it is them — and everything they ever ask you for is already there.
- Every invoice you have issued them, and the statement behind it
- A Pay button that actually charges, on the rail you chose
- The documents waiting for their signature
- Everything they have already signed, kept where they can find it
- A record of when they opened the invoice — so “we never received it” has an answer
The supplier portal
Watched by Payables
The mirror image, pointed the other way. Your suppliers stop emailing invoices into a shared mailbox that somebody has to empty by hand.
- The purchase orders you have sent them
- A place to submit an invoice against one, which you accept or send back
- An address they can simply email it to instead, if they prefer
- The agreements waiting for their signature
- Switches per company: open the portal, allow signing, accept email — or not
A link in their inbox and a code. No account, no password, nothing for them to install.
After the money lands
The half nobody demos.
Anyone can show you a Pay button. The question worth asking is what your accountant does on the first of the month, and whether it involves a spreadsheet.
Watched by
Collections
The payout is not the payment
A processor pays you one lump on Tuesday for forty charges, three refunds, a chargeback and its own fees. Import the payout report and each line is matched to the invoice it belongs to, the invoices are settled, the fees are posted, and the net drains against the bank line — to zero, or it is not reconciled.
A batch you can undo
A reconciled batch is locked, not merely marked. If it was wrong it is voided and reversed as one act — rather than by hand-editing forty settled invoices and hoping you found them all.
The bank, read directly
Connect the account and the statements arrive on their own; or import CAMT.053, Norma 43 or a CSV. Either way the lines are matched against what the books already expect, and what is left over is the short list worth a person’s attention.
Chasing, without the ritual
Reminders escalate on a ladder you set, a promise to pay puts a hold on the chasing until the date it promised, and a dispute stops it entirely instead of sending a fourth polite email into a fight.
Good to know
Two details that save you work.
Adyen, exactly as you have it
Already taking payments with Adyen? Change nothing: its payout reports are imported and reconciled here just like Stripe’s.
PayPal, as one more bank account
Every PayPal payment is booked with its fee the same day, and the balance is reconciled like a bank account — because it is money you can already use, including to pay your suppliers straight from it.
Bring an awkward payout.
The most useful demo is your own worst reconciliation — a real payout report with fees, a refund and something that does not match. That is where the difference shows.