🏪 Course 14: Merchant Payment Gateway PREMIUM

A payment gateway is the technology that sits between a customer who wants to pay and a merchant who wants to receive money. Think of it as a digital cashier — it securely captures payment information, validates the transaction, communicates with the financial network, and confirms the result back to both parties.

Every time you tap your credit card at a coffee shop, buy something online, or scan a QR code to pay, a payment gateway is working behind the scenes. It handles the complexity of authorization, fraud detection, currency conversion, and settlement so that merchants don't have to build these systems themselves.

The Core Functions of a Payment Gateway

Payment gateways exist because direct money transfers between strangers are inherently risky. The gateway acts as a trusted intermediary that ensures the customer's money actually reaches the merchant, while protecting both parties from fraud.

To appreciate why cryptocurrency payment gateways are revolutionary, you first need to understand how the traditional credit card system works. It's a surprisingly complex chain involving multiple intermediaries, each taking a cut.

The Visa/Mastercard Payment Flow

When a customer swipes their card at a store, the following happens in roughly 2-3 seconds:

• Customer Initiates Payment

  The customer taps, swipes, or enters their card details online. The POS terminal or website's payment form captures the card number, expiry date, and CVV.

• Gateway Encrypts and Transmits

  The payment gateway (e.g., Stripe, Square) encrypts the card data and sends an authorization request to the merchant's acquiring bank.

• Card Network Routes the Request

  The acquiring bank forwards the request through the card network (Visa, Mastercard, Amex) to the customer's issuing bank. The issuing bank checks the customer's available credit and fraud indicators.

• Authorization Response

  The issuing bank approves or declines the transaction. The response travels back through the card network, acquiring bank, and gateway to the merchant's terminal — all in about 2 seconds.

• Settlement (2-3 Business Days Later)

  At the end of the day, the merchant submits a "batch" of authorized transactions. Funds move from issuing banks through the network to the acquiring bank, which deposits them into the merchant's account — minus fees. This process takes 2-3 business days.

The Hidden Cost: Who Takes a Cut?

On a typical $100 credit card transaction, here's where the money goes:

Cryptocurrency payment gateways fundamentally change the payment equation by removing intermediaries. Instead of routing transactions through banks and card networks, crypto payments move directly on the blockchain — a public, decentralized ledger.

The Crypto Payment Flow

Here's how a cryptocurrency payment works compared to traditional cards:

• Customer Initiates Payment

  The customer scans a QR code or clicks a payment link. The gateway generates a unique payment address and displays the exact amount of cryptocurrency to send (calculated from the current exchange rate).

• Customer Sends Crypto from Their Wallet

  The customer confirms the transaction in their wallet app. The transaction is broadcast to the blockchain network. There is no bank involved, no credit check, and no card number to steal.

• Blockchain Confirms the Transaction

  Network nodes (miners or validators) verify the transaction and add it to a block. Depending on the blockchain, confirmation takes seconds (KENO) to minutes (Bitcoin). The gateway monitors the blockchain and detects the incoming payment.

• Merchant Receives Notification

  The gateway sends a webhook callback to the merchant's server confirming receipt. The merchant can choose to hold the crypto, convert to stablecoin, or cash out to fiat currency.

Key Advantages Over Traditional Systems

Payment Channel Networks: The Lightning Network

One innovation worth understanding is payment channel networks, most famously Bitcoin's Lightning Network. These are "Layer 2" solutions that process transactions off the main blockchain for speed and lower fees, then settle the net result on-chain later.

The concept is like running a bar tab: instead of paying the bartender for every individual drink (each requiring a blockchain transaction), you open a "tab" (payment channel), order multiple drinks, and settle the final total at the end. This reduces on-chain congestion and enables near-instant micropayments.

Kenostod's blockchain processes transactions quickly enough that Layer 2 isn't required for most merchant use cases. However, understanding payment channels is important for comparing platforms and evaluating future scaling strategies.

The Kenostod Merchant API is a RESTful interface that allows businesses to programmatically create invoices, generate payment addresses, track transaction status, and manage their merchant account. It's designed to be developer-friendly while maintaining enterprise-grade security.

API Architecture Overview

The API follows a request-response model over HTTPS. All requests require authentication via API keys, and all responses are in JSON format. The base URL for the API is:

Core API Endpoints

1. Create a Payment Invoice

2. Check Payment Status

3. Webhook Notification

When a payment is received, Kenostod sends a POST request to your configured webhook URL:

Before a business can start accepting KENO payments, it must complete the merchant onboarding process. This involves identity verification (KYC), business validation, and configuration of payment settings.

Know Your Customer (KYC) Requirements

KYC is a regulatory requirement designed to prevent money laundering, terrorism financing, and fraud. All payment gateways — whether traditional or crypto — must comply with KYC regulations in the jurisdictions where they operate.

Individual Merchant Requirements

• Government-issued photo ID (passport, driver's license, or national ID)
• Proof of address (utility bill or bank statement dated within 90 days)
• Tax identification number (SSN, EIN, or local equivalent)
• Bank account details for optional fiat settlement

Business Merchant Requirements

• Business registration documents (certificate of incorporation, business license)
• Proof of business address
• Beneficial ownership information (anyone owning 25%+ of the business)
• Description of products/services offered
• Estimated monthly transaction volume

The Onboarding Process

• Submit Application

  Fill out the merchant registration form with business details, upload KYC documents, and specify your intended use case (e-commerce, retail, services, etc.).

• Automated Verification

  Kenostod's system performs initial document verification, cross-references against sanctions lists, and runs basic fraud checks. Most applications are processed within 24 hours.

• Manual Review (if needed)

  High-risk categories (gambling, adult content, firearms) or unusual applications receive manual review by the compliance team. This may take 3-5 business days.

• Account Activation

  Upon approval, you receive your API keys (test and live), access to the merchant dashboard, and can begin accepting payments.

QR codes are the bridge between the physical and digital worlds of cryptocurrency payments. They encode payment information into a scannable image, making it as easy to pay with KENO as it is to scan a barcode at the grocery store.

How QR Code Payments Work

• Merchant Generates QR Code

  Through the dashboard or API, the merchant creates a QR code containing the payment address, amount in KENO, and an invoice reference ID. Static QR codes can be printed for fixed-price items; dynamic QR codes are generated per transaction for variable amounts.

• Customer Scans with Wallet App

  The customer opens their Kenostod wallet app and scans the QR code. The app automatically populates the payment address and amount — no manual entry needed, eliminating typo errors.

• Customer Confirms Payment

  The customer reviews the payment details and confirms. The transaction is signed with their private key and broadcast to the KENO network.

• Real-Time Confirmation

  The merchant's POS terminal or dashboard updates in real-time as the transaction is confirmed on-chain. A chime or visual indicator signals successful payment.

Invoice Generation System

The invoicing system supports both simple and complex billing scenarios:

Simple Invoice (Single Item)

Itemized Invoice (Multiple Line Items)

Settlement is the process of transferring the payment from the customer's wallet to the merchant's account. With Kenostod, merchants have multiple options for how they receive and manage their funds.

Settlement Options

Option 1: Hold as KENO

The simplest option. Payments arrive directly in your merchant wallet as KENO tokens. This is ideal for merchants who believe in KENO's long-term value or who have KENO-denominated expenses (like paying KENO-accepting suppliers).

• Pros: Zero conversion fees, instant settlement, maintain exposure to KENO appreciation
• Cons: Subject to KENO price volatility, may need to convert later for fiat expenses

Option 2: Auto-Convert to Stablecoin (PUSD)

Kenostod can automatically convert received KENO to PUSD (a USD-pegged stablecoin) at the moment of receipt. This locks in the USD value and eliminates price volatility risk.

• Pros: Price stability, still on-chain, easy to convert to fiat later
• Cons: Small conversion fee (0.1%), miss out on KENO price increases

Option 3: Auto-Convert to Fiat (USD/EUR/GBP)

For merchants who need traditional currency, Kenostod partners with licensed exchange partners to offer automatic conversion to fiat with direct bank deposit.

• Pros: Familiar currency, easy accounting, no crypto management needed
• Cons: Conversion fee (0.5%), bank deposit takes 1-2 business days

Option 4: Split Settlement

The most flexible option. Configure a split: for example, hold 50% as KENO and convert 50% to USD. This balances growth potential with operational cash flow needs.

Kenostod's fee structure is designed to reward merchants who grow their KENO payment volume. The more transactions you process, the lower your fees become — creating a positive feedback loop that benefits both the merchant and the KENO ecosystem.

The 4-Tier Program

Fee Comparison: Kenostod vs. Competitors

Understanding Your Tier Savings

Let's see the real impact of tier progression on a business doing $100,000/month in KENO payments:

Pricing Models for Merchants

Kenostod supports two pricing approaches that merchants can choose from:

Auto-Pricing (Exchange Rate)

Set prices in USD and let the gateway automatically calculate the KENO amount at the current exchange rate. Best for merchants who think in fiat terms and want stable revenue.

KENO-Native Pricing

Set prices directly in KENO. Best for crypto-native businesses or when targeting KENO-holding customers who prefer to think in token terms.

Security is paramount when handling payments. A single breach can destroy customer trust and potentially expose a business to massive liability. Kenostod's merchant gateway is designed with security-first principles.

API Key Management

Kenostod uses a dual-key system for API authentication:

Security Best Practices

• Never Expose Secret Keys in Frontend Code

  Your secret key should only exist on your server. Never include it in JavaScript bundles, mobile app code, or version control (git). Use environment variables to store keys.

• Rotate Keys Regularly

  Rotate your API keys every 90 days. The Kenostod dashboard supports seamless key rotation with a grace period where both old and new keys work simultaneously.

• Restrict API Key Permissions

  Use IP whitelisting to restrict which servers can use your API keys. Set spending limits and configure alerts for unusual activity.

• Verify All Webhook Signatures

  Compute the HMAC-SHA256 of the webhook payload using your webhook secret and compare it to the signature header. Reject any request with an invalid signature.

• Use HTTPS Everywhere

  All API calls and webhook endpoints must use HTTPS. Never transmit payment data over unencrypted HTTP connections.

PCI DSS Compliance Considerations

PCI DSS (Payment Card Industry Data Security Standard) is a set of security standards designed to protect cardholder data. While Kenostod doesn't process credit cards directly, merchants who accept both crypto and card payments need to understand PCI compliance.

If you also accept credit cards alongside KENO, you still need PCI compliance for the card processing portion. The recommended approach is to use a PCI-compliant payment processor (like Stripe) for cards and Kenostod for crypto, keeping the two systems separate.

Understanding how Kenostod compares to established crypto payment platforms helps merchants make informed decisions. Let's examine the three major options:

These case studies illustrate the real challenges and opportunities of merchant cryptocurrency adoption:

Complete these exercises to reinforce your understanding. Take your time — thoughtful answers demonstrate true comprehension.