Meta tags:
description=;

Headings (most frequently used words):

api, keys, in, what, are, key, everypay, public, private, to, pos, your, credentials, when, share, each, where, find, and, dashboard, security, best, practices, for, sharing, accessing,

Text of the page (most frequently used words):
keys (39), api (37), your (30), everypay (16), are (13), the (12), with (11), and (10), key (9), integration (9), payment (8), payments (8), they (8), #private (7), pos (7), for (7), account (7), access (7), pay (7), payform (6), use (6), credentials (6), these (6), public (5), secure (5), sensitive (5), share (5), data (5), application (5), what (4), can (4), servers (4), operations (4), code (4), authenticate (4), that (4), like (4), app (4), overview (4), direct (4), apple (4), accessing (3), security (3), from (3), settings (3), generate (3), dashboard (3), you (3), external (3), developers (3), backend (3), never (3), safe (3), but (3), ensure (3), client (3), side (3), when (3), must (3), shared (3), environments (3), unauthorized (3), actions (3), perform (3), enable (3), processing (3), refunds (3), requests (3), used (3), handled (3), them (3), services (3), cases (3), transactions (3), transaction (3), guide (3), started (3), iris (3), google (3), best (2), practices (2), sharing (2), sandbox (2), main (2), menu (2), select (2), under (2), section (2), here (2), log (2), find (2), follow (2), where (2), limited (2), only (2), partners (2), frontend (2), publicly (2), critical (2), level (2), issuing (2), case (2), purpose (2), applications (2), avoid (2), not (2), safely (2), communication (2), care (2), prevent (2), physical (2), link (2), devices (2), platform (2), person (2), allow (2), process (2), unique (2), securely (2), environment (2), variables (2), secret (2), tools (2), making (2), getting (2), 1155 (2), options (2), search (2), 2026, this, page, new, click, existing, listed, view, navigate, directly, steps, collaborating, consider, creating, restricted, permissions, within, anyone, outside, organization, unless, absolutely, necessary, include, website, javascript, paired, validation, configure, forms, widgets, trusted, working, each, exposed, included, unsecured, compromised, lead, financial, loss, reminder, full, allowing, such, server, confidential, exclusively, while, facing, should, still, responsibly, exposing, places, misused, important, expose, typically, initiate, workflows, embedding, form, identify, using, meant, both, act, tokens, fraudulent, activity, retail, real, time, manage, point, sale, terminals, issue, fetch, between, interacting, online, store, management, hardcoded, including, documents, emails, repositories, github, even, repos, keep, need, collaborate, consultants, how, protect, business, customers, guidelines, stays, authorized, apps, valid, knows, request, recognized, passwords, cards, our, ensuring, backbone, connection, think, identifiers, communicate, unlock, world, possibilities, integrating, solutions, more, emulator, reference, webhooks, test, notifications, testing, seller, kyc, basic, concepts, marketplace, terminal, onboarding, ecr, 1098, erp, going, live, invoicing, providers, greek, compliance, subsequent, mit, initial, recurring, tokenization, tokenize, card, tokenized, opencart, prestashop, magento2, woocommerce, shopify, commerce, platforms, native, other, methods, examples, special, callbacks, functions, accept, introduction, get, documentation,

Text of the page (random words):
api credentials everypay documentation search search get started introduction sandbox account api credentials accept payments payform integration options functions callbacks special cases examples direct api other payment methods google pay google pay payform google pay direct integration apple pay apple pay payform apple pay native apple pay direct iris iris payform iris direct integration e commerce platforms overview shopify woocommerce magento2 prestashop opencart tokenized payments tokenize a card payform integration guide options tokenization recurring payments initial transaction subsequent transaction mit in person payments overview getting started greek compliance integration guide a 1155 e invoicing providers going live erp integration a 1155 ecr integration a 1098 terminal onboarding process marketplace link overview getting started basic concepts seller kyc integration testing payment notifications overview api integration guide tools test cases webhooks api reference pos emulator more api credentials api keys in everypay api keys are the backbone of your connection to everypay s payment platform think of them as the unique identifiers that allow your application to securely communicate with everypay s services they unlock a world of possibilities for integrating payment solutions but must be handled with care to ensure the security of your transactions and sensitive data what are api keys api keys are like the passwords or access cards for your everypay account they authenticate your app when making requests to our servers ensuring that your application is recognized everypay knows it s your app making the request your requests are valid only authorized apps can perform actions like processing payments or issuing refunds your data stays secure api keys prevent unauthorized access to your account and transactions security best practices for sharing api keys if you need to collaborate with external developers consultants or partners here s how to do it safely to protect your business and your customers follow these key guidelines keep api keys secret never share your api keys publicly avoid including them in shared documents emails or code repositories like github even in private repos use environment variables store api keys securely in environment variables or secret management tools so they re not hardcoded in your application your api keys in everypay api keys api keys are unique credentials that authenticate your application when interacting with everypay s services online they enable secure communication between your app and everypay s servers allow your app to process payments issue refunds and fetch transaction data pos keys pos keys are used to authenticate and manage physical devices like point of sale terminals for in person payments they link your pos devices with everypay s platform for real time payment processing ensure secure transactions in physical retail environments in both cases these keys act as access tokens to enable safe communication but they must be handled with care to prevent unauthorized access or fraudulent activity what are public api keys public api keys are meant to be shared safely in client side applications these keys purpose identify your account and the application using everypay s services use case typically used in frontend code to initiate payment workflows e g embedding a payment form level of access limited to operations that do not expose sensitive data or perform critical actions important while these keys are safe to share in public facing environments they should still be handled responsibly avoid exposing them in places where they can be misused what are private api keys private api keys are confidential credentials used exclusively in backend applications these keys purpose authenticate requests from your server to everypay s servers use case enable secure operations such as processing payments issuing refunds or accessing sensitive account data level of access full access to your account allowing it to perform sensitive operations critical reminder private api keys must never be exposed in client side code shared publicly or included in unsecured environments a compromised private key can lead to unauthorized actions and financial loss when to share each key public api key share with trusted developers or external partners working on your frontend code use it to configure client side payment forms or widgets safe to include in your website s javascript but ensure it is paired with backend validation private api key never share with anyone outside your organization unless absolutely necessary use only within your secure backend servers for sensitive operations if you re collaborating with external developers consider creating restricted keys with limited permissions where to find api keys and pos keys in your dashboard you can find your api keys and pos keys directly in the everypay dashboard follow these steps accessing api keys log in to the dashboard use your everypay credentials to log in navigate to settings from the main menu select api keys under the settings section view or generate keys from the main menu select api keys under the settings section existing keys are listed here to generate a new key click generate key sandbox account payform on this page what are api keys security best practices for sharing api keys your api keys in everypay api keys pos keys public api key private api key accessing api keys everypay 2026