# Payneteasy Key Pair Factory: Generate API Key Pairs in a Few Clicks Source: https://payneteasy.com/blog/payneteasy-key-pair-factory _Generate the API key pair for Payneteasy Payout API and the virtual terminal in a few clicks — no cryptography expertise required._ 10.06.2026 2 min read Table of contents 1. [The hidden hurdle in every integration](#key-hidden-hurdle) 2. [What the app does](#key-what-app-does) 3. [Why it matters](#key-why-it-matters) 4. [Flexibility without the friction](#key-flexibility) Contact author Generating the API key pair for the Payneteasy Payout API and the virtual terminal used to be an expert-only OpenSSL chore. The Payneteasy Key Pair Factory turns it into a few clicks — no cryptography expertise required. ## The hidden hurdle in every integration Connecting to a payment gateway is rarely blocked by business logic. More often, it's blocked by the very first technical step: request authentication. To call the Payneteasy API securely, every request must be signed — and that means producing a cryptographic key pair and a correctly built OAuth signature. In practice this involves generating an RSA key pair (often via OpenSSL), converting it between PKCS#8 and PKCS#1 containers, assembling a signature base string, percent-encoding it correctly, signing it with RSA-SHA256 or HMAC-SHA1, and packing everything into the Authorization header. The full manual key generation flow is described in the [Payneteasy API documentation](https://doc.payneteasy.com/integration/general_api_usage/request_authentication_methods/oauth.html#generating-key-pair). One wrong character and the request is rejected. For a team without a cryptography specialist, this single step can turn a one-day integration into a one-week support thread. ## What the app does The Payneteasy Key Pair Factory removes that step entirely. It produces the key pair a merchant needs to authenticate with the platform — the keys required to connect to the Payout API and to initiate payouts through the virtual terminal in the personal cabinet. Instead of installing OpenSSL, memorizing command flags and matching key formats by hand, the merchant gets the right keys in the right format, ready to use, in a few clicks. The private key stays with the merchant; the public key is what Payneteasy uses to verify each signed request. The app is available as a public [GitHub repository](https://github.com/payneteasy/key-pair-factory) and can be downloaded from there. ## Why it matters Faster onboarding, fewer integration mistakes, and fewer support requests. By removing the hardest manual step, the app helps merchants complete their connection to the system sooner and with less back-and-forth during onboarding. ## Flexibility without the friction Payneteasy has always stood for depth: granular configuration, multiple authentication methods, and the flexibility that demanding payment businesses require. Historically, that depth came at a cost — complexity was the entry ticket. Now that is changing. By investing in better tooling, we are keeping every bit of the flexibility while stripping away the friction that used to surround it. The Payneteasy Key Pair Factory is one concrete example: a hard, expert-only task turned into a simple, self-service action, without a massive engineering project behind it. Power and simplicity, finally on the same side. ## Get started If you're integrating the Payout API or working with payouts through the virtual terminal, the Payneteasy Key Pair Factory is the fastest way to get authenticated. Talk to our team to enable it for your account: **Contact Us**. ## Related products - [Payneteasy Payment Gateway (Acceptance)](/solutions/gateway) — A white-label payment gateway that lets your customers earn more while you grow turnover and boost your profits. - [Payment Orchestration Platform (PSP)](/solutions/orchestration-payment-platform) — Consolidate all your payments, increase acceptance rates, and get precise financial reporting and reconciliation across providers. - [Leads Protection System (Security)](/solutions/leads_protection_system) — Separate and encrypt personal data in a private, secured cloud — stay GDPR compliant without changing how your team works.