canonical: https://jentic.com/apis/frankiefinancial.io/frankie-financial # Frankie Financial API Frankie Financial is a KYC, KYB, and AML compliance utility used by Australian and New Zealand banks, fintechs, and insurers to onboard customers and businesses. The API exposes 46 endpoints across entity verification, document scanning and comparison, business ownership lookups, PEP and sanctions screening, fraud blacklists, and selfie checks. It validates Australian driver's licences, passports, Medicare cards, electricity bills, NZ driver's licences, Chinese bank cards, and a range of international identity documents. ## For AI agents Run KYC, KYB, AML, and document verification checks for Australian and international entities, including PEP, sanctions, and watchlist screening. Authentication is an api_key header. ## Scope Does not handle payment processing, card issuance, or open-banking data feeds - use for KYC, KYB, AML, and document verification checks only. ## Capabilities - Verify an individual's name, address, and date of birth against national databases - Scan and validate Australian driver's licences, passports, Medicare cards, and visas - Run PEP, sanctions, watchlist, and adverse-media screening on an entity - Query organisation ownership and run KYC checks on shareholders and beneficial owners - Compare a selfie against the photo on a scanned identity document - Flag entities to a blacklist or check them against a fraud background list - Pull a business credit score and credit report ## Use cases ### Australian Bank Account Onboarding An Australian neobank verifies new customers in under a minute by submitting name, date of birth, and address through Frankie Financial's entity verification, then scanning a driver's licence and running a selfie comparison. The API consolidates results from multiple national databases and returns a single pass/fail decision plus the underlying check evidence for audit. Example prompt: POST to /entity with the customer's name, DOB, and address, then POST `/document/new/scan` with the licence image and run `/document/{documentId}/compare` against the selfie ### KYB and Beneficial Ownership A business lender runs KYB on a corporate borrower by querying ownership through Frankie Financial, then runs KYC and AML screening on every director and beneficial owner above a 25% threshold. The API surfaces the ownership graph, credit reports, and any PEP or sanctions hits in a single workflow. Example prompt: POST `/business/ownership/query` with the ABN, then for each beneficial owner POST `/entity/new/verify` with the appropriate checkType to run AML screening ### Document and Selfie Verification A digital insurer asks the customer to photograph their licence and take a selfie. Frankie Financial scans the document, extracts the fields, validates against the issuing authority, and compares the selfie against the document photo to confirm the holder is present. The full check completes asynchronously and resolves in seconds. Example prompt: POST `/document/new/scan` with the licence image, then POST `/document/new/compare` with the selfie image and check the comparison verdict ### AI Agent Compliance Workflow A compliance agent triages onboarding events from a fintech queue. For each new applicant, the agent uses Jentic to call Frankie Financial's entity, document, and AML endpoints, summarises the verdicts in plain language, and routes high-risk cases to a human reviewer. The api_key never enters the agent's context. Example prompt: Search Jentic for 'run a KYC check on an Australian customer', load the entity verification schema, execute against the new applicant, and post a summary back to the queue ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/entity` | Create an entity and start identity verification | | POST | `/entity/new/verify/{checkType}/{resultLevel}` | Run a typed verification check on a new entity | | POST | `/document/new/scan` | Scan and extract fields from an identity document | | POST | `/document/new/compare` | Compare a selfie against a scanned document | | POST | `/business/ownership/query` | Query beneficial ownership for a business | | GET | `/entity/{entityId}/checks` | Retrieve all checks run against an entity | | POST | `/entity/{entityId}/flag/blacklist` | Flag an entity to the shared blacklist | ## Key resources - **Entity** — Create, search, and run identity and AML checks on individual entities - **Document** — Scan, compare, and verify identity documents and utility bills - **Business** — Run KYB, ownership lookups, and international company searches - **Industry** — Industry-specific checks such as Australian electricity retailer comparison - **Push Notification** — Mobile push verification flows tied to an entity - **Flag** — Manage blacklist flags and fraud lists for entities ## Why Jentic - **Setup:** Wiring the Frankie Financial API by hand means setting its api_key header on every call and building your own retry and error handling across dozens of KYC, KYB, AML, and document endpoints. Through Jentic you install once, import Frankie Financial from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Frankie Financial puts the entity id in the URL path (`/entity/{entityId}/...`), so a rule can pin your agent to one entity: it can read that entity's checks and run verification for it. You choose the operations it may call, so adding an entity to the blacklist is not included unless you add it. - **Credential handling:** Your Frankie Financial api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'verify an Australian driver licence' or 'run AML screening', and Jentic returns the matching Frankie operation with its input schema so the agent runs the right check without parsing all 46 endpoints. ## Related APIs - **ComplyAdvantage** — ComplyAdvantage focuses on AML, sanctions, and adverse-media screening with a global remit - **Onfido** — Onfido provides global document and biometric verification with strong selfie liveness - **Sumsub** — Sumsub offers a configurable orchestration layer that can call Frankie checks alongside other providers - **Experian** — Experian provides credit data that complements Frankie's identity and AML checks ## FAQ ### What authentication does the Frankie Financial API use? Frankie Financial uses an API key passed in the api_key header. Production access also requires a signed commercial agreement and a customer ID. Through Jentic, the api_key is stored encrypted in the vault and replaced with a scoped execution token before the agent runs. ### Can I verify an Australian driver's licence with the Frankie Financial API? Yes. POST the licence image or details to `/document/new/scan` to extract and validate the fields, then call `/document/{documentId}/verify` to confirm the licence against the issuing authority's database. The verification verdict and underlying evidence are returned for audit. ### What are the rate limits for the Frankie Financial API? Frankie Financial does not publish public rate limits in its OpenAPI spec. Production limits are negotiated as part of the commercial agreement and typically range from a few requests per second on standard plans up to bulk batch volumes for enterprise customers. ### How do I run a beneficial ownership check through Jentic? Search Jentic for 'beneficial ownership lookup', load the Frankie Financial `/business/ownership/query` schema, and execute it with the company identifier (ABN for Australia, registration number for international). Then loop the returned owners through `/entity/new/verify` for KYC and AML screening. ### Is the Frankie Financial API free? Frankie Financial does not offer a free production tier. A sandbox at api.demo.frankiefinancial.io is available with canned data once initial commercial discussions begin, and production pricing is per-check across the KYC, KYB, AML, and document modules. ### How do I screen a customer against PEP and sanctions lists? Create the entity at /entity, then POST `/entity/new/verify/{checkType}/{resultLevel}` with checkType set to the AML or watchlist option. The response returns a list of any hits along with the source list and the matched record so the compliance officer can disposition the case. ### Can I limit what my agent is allowed to do with the Frankie Financial API? Yes. Because you run Jentic One yourself, your own rules decide which Frankie Financial operations and credentials the agent may use. Since the entity id sits in the URL path (`/entity/{entityId}/...`), you can pin the agent to a single entity so it only reads that entity's checks and runs verification for it. You choose the operations it may call, so a sensitive action like flagging an entity to the blacklist stays off limits unless you explicitly allow it.