The approval becomes a documenta bank can check itself.

Q: Can a bank verify the certificate without Advanta?

Yes. Take the four fields, apply sha256 in the published order, compare. The banker portal does exactly that, and so does the evidence pack; neither trusts the other.

When a buyer approves an invoice, or a debtor acknowledges a notice of assignment, Advanta writes it as an acceptance certificate: who decided and when (for a debtor acknowledgment, also from which IP), with a fingerprint the bank portal and the evidence pack reproduce independently. Nobody has to trust a screenshot.

For banks → For buyers

sha256/v1 fingerprintIP address and time recordedSingle-use token, 90-day link expiry

Acceptance certificate · cession notice · demo record

Cerámicas Levante, S.L.

Debtor · NIF B46209151 · fictional company, demo data

Invoices3 · €11,685.00

Notice sent2026-08-20 11:30 UTC

Acknowledged2026-08-20 12:32 UTC

FromIP address recorded

Tokensingle use, valid for 90 days

Fingerprint · sha256/v1
137bc97633297ba65be2fe9a353f3a5d
edf47903df0fa65294a39850f041d83f

4 fieldsone fingerprint

sha256/v1version-tagged

2 systemsrecompute it independently

UTCtimestamp; IP for debtor acknowledgments

90 daysacknowledgment link expiry

[01] What it records

Four facts, one fingerprint.

The certificate is deliberately small. It records a decision and the circumstances of that decision, and it makes them reproducible. It does not interpret them.

The decisionA buyer’s approval, or a debtor’s acknowledgment.

Written at the moment it happens, by the platform, not typed later by a person. kind · buyer approval · cession notice

When, from whereUTC timestamp on every record; IP and single-use token on a debtor acknowledgment.

A buyer approval records the user who approved and the time. UTC · user · IP · token

The fingerprintsha256 over four fields.

The record id, the debtor’s NIF, the acknowledgment time and the total amount. Version-tagged, so the formula can evolve without breaking old certificates. sha256/v1 · id | NIF | time | amount

Who can verifyThe funder’s portal and the evidence pack, independently.

Both compute the fingerprint from the same four fields. If either differs from the certificate, something changed.

[02] The second gate

Nothing counts until operations mark the source as real.

A certificate proves an acceptance happened. Demand evidence proves it happened in a real business. The two are kept apart on purpose: every tenant is marked real, demo, test or internal, and only real counts. Demo, test and internal books are left out of every pack, and the exclusion itself is listed. When the pack reports zero, it is sent reporting zero.

tenantCerámicas Levante

classificationreal?

evidencehashed · pseudonymised

packSHA-256 manifest

● only real counts

demo · test · internal → excluded, and listed

[03] What it is not

A record of acceptance, not a guarantee of payment.

Its contractual effect depends on the underlying agreement and on the law of the jurisdiction, and the notice wording is being reviewed by counsel in each market. It does not replace the contract, the invoice or the notice itself; it makes them verifiable.

RecordsDecision, timestamp, user or IP, fingerprint.

Facts, at the moment they happen.

Does not decideWhether the debtor will pay, or what the contract says.

The notice wording is being reviewed by counsel in each market.

StoredIn the EU, under row-level security. Users can read their records, not change them.

eu-west-1 · RLS · read-only for users.

FAQ Questions credit committees ask us

Before you fund against it.

Can a bank verify the certificate without Advanta?

Yes. Take the four fields, apply sha256 in the published order, compare. The banker portal does exactly that, and so does the evidence pack; neither trusts the other.

Is it legally binding?

It is a record of acceptance. Its contractual effect depends on the underlying agreement and the jurisdiction; the wording of the notice of assignment is being reviewed by counsel in each market. The certificate makes the facts verifiable; it does not create obligations on its own.

What if the debtor disputes it later?

The record shows what was acknowledged, when, and from which IP address, with a fingerprint that would not match if any field had changed. A dispute is then about the facts, not about whether they were recorded.

Where is it stored?

In the EU (eu-west-1), under row-level security: users can read their records but not change them. Security →

Is the example above real?

It is a demo record on a fictional debtor, fingerprinted with the production formula. Real records are never shown publicly.

See it in the banker portal.

Book 30 minutes

A sandbox walk-through: an approval, the certificate it produces, and the pack that carries it.

Book 30 min ↗

The bank’s seat

Your factoring and confirming deals, with this document on every one.

For banks →

reply within <1 business day · diogo@advanta.pt