Step 1
Define the decision
Your service sends who is asking, what they need, which policy version applies, and channel context. The format is the same for live API calls and offline packets.
Strong customer authentication at transaction time
A verification layer that returns signed outcomes when policy requires step-up, device binding, or consent confirmation. AffixIO complements your authentication provider; it does not replace it.
Short answer: Your identity provider handles login. AffixIO answers whether this specific transaction or action is permitted under current policy and returns proof for audit.
Stateless verification · Signed yes/no outcomes · No standing PII store
Industry context
PSD2 and UK payment rules require strong customer authentication for many electronic payments. Banks implement SCA through app, SMS, or hardware tokens, then still need a clear record that policy matched the attempt.
What security and product teams face
Authentication success does not always mean the subsequent payment action is in scope. Product teams need a separate, auditable decision at the moment of payment.
AffixIO approach: After your customer authenticates, AffixIO evaluates transaction constraints and returns yes or no with proof. The model supports dynamic linking narratives where policy requires action-specific verification.
Where verification applies
- Card payments
Confirm transaction amount and payee policy before authorisation.
- Open banking payments
Verify initiation requests against customer consent records.
- High-value transfers
Enforce limits and step-up outcomes with signed evidence.
- Wallet and token provisioning
Binary eligibility before token activation.
- Corporate banking
Dual control and mandate checks with proof for audit.
From request to verified outcome
The same three-step model used across AffixIO applies here: describe the decision, evaluate against sources you control, return yes or no with proof.
Step 2
Evaluate against authority
Checks run against registries and rules you authorise. Sensitive fields stay in systems you already operate wherever the design allows.
Step 3
Return yes or no with proof
The response is explicit, signed where required, and suitable for audit or partner handoff. AffixIO does not retain the request after the decision.
Where AffixIO sits in your banking stack
A thin stateless layer between channels, agents, and your core systems. AffixIO answers verification questions at transaction time; it does not replace core banking, card processing, or your identity provider.
Your channelsMobile banking, internet banking, contact centre tools, merchant portals, partner APIs, and software agents acting on behalf of customers.
AffixIOStateless verification via API and SDK. Binary yes or no outcomes with cryptographic proof suitable for audit.
Your core systemsCore banking, card authorisation, CRM, risk engines, KYC vendors, and directories you already accredit.
Further reading: technical architecture, what AffixIO is, banking systems integration.
What you can implement today
Transaction binding
Attempts tied to amount, merchant, and time windows where configured.
Consent receipts
Machine-readable scope for agent and recurring payments.
Offline validation
Signed proofs where branches lack continuous connectivity.
Example response (illustrative)
{
"eligible": true,
"proof": "<signed verification artefact>",
"decision_id": "dec_…",
"evaluated_at": "2026-05-15T12:00:00Z"
}
OpenAPI documentation: api.affix-io.com. Integrate via REST, webhooks, or SDKs.
How teams deploy
Managed API
Connect through your API gateway with TLS, mutual authentication where required, and departmental logging.
Self-hosted
Run inside your accredited boundary when policy requires on-premise or private cloud.
Offline and edge
Validate signed proofs locally where connectivity is limited. See offline verification.
Agentic channels
Machine clients receive the same binary signals as citizen channels. See M2M verification.
Deploy behind your API gateway with TLS and mutual authentication where your security policy requires it. Managed API and private cloud options are available.
Cryptography and data handling
Built for long-lived programmes that must plan beyond legacy signatures and minimise data held at the verification boundary.
Stateless by design
No long-term store of who asked or the attributes inside a request. Supports proportionate DPIA narratives.
Post-quantum ready
Verification artefacts can use quantum-resistant signing aligned with industry post-quantum direction, with optional enterprise key management where your policy requires it.
Zero-knowledge outcomes
Where policy allows, demonstrate that a rule evaluated to yes without exporting underlying registry content.
Patent pending: AffixIO verification pipeline protected under GB2510622.0 (pending).
Regulatory and assurance alignment
AffixIO is designed to support data-minimization narratives common in financial services assurance. Your legal and compliance teams remain responsible for licensing, scheme rules, and supervisory filings.
- UK GDPR and EU GDPR aligned data handling (stateless request model)
- PCI DSS scope reduction through not storing cardholder data at the verifier
- PSD2 strong customer authentication patterns (verification at transaction time)
- AML programme support via binary eligibility without duplicating customer files
- SOC 2 and ISO 27001 compatible deployment models (managed API or private cloud)
- Pseudonymised audit metadata for security operations and internal audit
See GDPR compliance, PCI and data minimization, and privacy policy.
Common questions
Does AffixIO store customer personal data?
No. AffixIO is stateless verification infrastructure. It evaluates a request against sources you authorise and returns a signed yes or no with proof. It does not maintain a standing database of customers or request payloads.
Is AffixIO a bank, payment scheme, or regulated financial institution?
No. AffixIO provides verification infrastructure via API and SDK. Licensing, scheme membership, and supervisory obligations remain with your organisation.
Can verification work offline for branches and field teams?
Yes. Signed proofs can be validated where connectivity is limited, with reconciliation when the device or site is back online. See offline banking payments and offline payment verification pages.
How does AffixIO relate to our existing KYC vendor?
AffixIO is a decision and proof layer. Your KYC and AML vendors, core banking, and directories remain systems of record. AffixIO returns binary outcomes at the point of need without copying full customer files into another datastore.
Speak with our banking team
Share your channel mix, regulatory constraints, and first verification use case. We will respond with a practical integration outline.
AffixIO is an independent verification technology provider. References to regulations, schemes, and industry roles describe integration patterns; they do not imply certification, scheme membership, or endorsement by any bank or network. Production deployment is subject to your security, legal, and procurement review.