canonical: https://jentic.com/apis/blinkpayment.co.uk/blinkpayment # Blinkpayment Blink Card Present API The Blink Card Present API processes in-person card payments captured on a connected point-of-sale terminal. Its single operation submits a card-present sale for authorization with the amount and transaction details. Requests authenticate with HTTP Basic credentials over a sandbox or production host. ## For AI agents Submit an in-person card-present sale for authorization on a connected point-of-sale terminal. ## Scope Does not handle refunds, online card payments, or settlement reporting - use for in-person card-present sale authorization only. ## Capabilities - Submit an in-person card-present sale for authorization - Send the transaction amount and details for a terminal payment - Process point-of-sale card payments over a sandbox or production host ## Use cases ### In-person card sale A retail integration needs to charge a customer's card at the counter. The Blink Card Present API submits the sale with its amount and transaction details for authorization on a connected terminal and returns the result. Example prompt: Submit a card-present sale via POST `/v1/card-present/sales` with the amount and terminal reference ### Sandbox integration testing Before going live, a point-of-sale integration needs to exercise the payment flow safely. The sandbox host accepts the same sale operation so a developer can verify the request and response shape without moving real money. Example prompt: Submit a test sale to the sandbox host and confirm the authorization response ### AI agent point-of-sale checkout An AI agent driving a checkout station can capture card-present sales without hand-wiring the Basic auth header. Through Jentic the agent discovers the sale operation by intent and calls it with the stored credential. Example prompt: Search Jentic for 'process a card-present sale', load the schema, and authorize a counter payment ## Key resources - **Card-present sales** — Submit an in-person card sale for authorization on a terminal ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 76 / 100 - AI-Readiness & Agent Experience: 34 / 100 - Agent Usability: 94 / 100 - Security: 10 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/blinkpayment.co.uk/blinkpayment/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Blink Card Present API by hand means setting the HTTP Basic header on every request and shaping the sale payload yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it. - **Permission scoping:** The Blink Card Present API takes its inputs in the request body rather than a resource id in the URL path, so you limit the agent to the sale operation it needs. You credit the agent only with the operations you allow, so anything you have not granted stays out unless you add it. - **Credential handling:** Your the Blink Card Present credential 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 'process a card-present sale', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing docs. ## Related APIs - **Square API** — In-person and online payments with terminal and reader support - **Stripe API** — Card processing across online and in-person channels - **Xero Accounting API** — Accounting to record and reconcile card takings ## FAQ ### What authentication does the Blink Card Present API use? The Blink Card Present API authenticates with HTTP Basic credentials sent on each request. Through Jentic those credentials are stored encrypted in your own instance and injected at run time, so the raw values never reach the agent's context. ### Is there a the Blink Card Present API MCP server? You don't need an MCP server to give your agent the Blink Card Present API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec. ### What does the Blink Card Present API do? It submits an in-person card-present sale for authorization on a connected point-of-sale terminal, sending the amount and transaction details and returning the authorization result. A sandbox host is available for testing. ### Can I limit what my agent is allowed to do with the Blink Card Present API? Yes. Because you run Jentic One yourself, your own rules decide which the Blink Card Present API operations and credentials the agent may use. You grant only the operations it needs, such as submitting a card-present sale, so any operation you have not granted stays off limits unless you add it. The choice of what the agent may call is yours. ### How do I connect my agent to the Blink Card Present API through Jentic? Search Jentic by intent such as 'process a card-present sale' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.