Getting Started
Understand the Genuka Pay integration flow before making your first API call.
Introduction
Genuka Pay gives your product a single integration surface for collections, payouts, webhook-driven state updates, and compliance-aware account activation.
If you are integrating for the first time, use this reading order:
- retrieve your application credentials
- authenticate requests securely
- create a payment or payout flow
- consume webhooks for asynchronous updates
- complete KYC before production rollout
Authentication
Learn how your application secret key and environment headers work together.
Payments
Initiate collections, track status, and model customer payment flows correctly.
Payouts
Send funds to recipients with either saved payment methods or direct recipient details.
KYC and Activation
Understand how compliance status and limits affect your ability to operate live traffic.
Recommended path
Start with Quick Start, then read Authentication, and only after that move into the API reference.
Core Concepts
Application
Your integration is attached to an application. The application is the source of:
- a
public_key - a
secret_key - an
environment - credential rotation history
Payments
Collections are created through the Payments API. Each initiated payment receives a stable transaction identifier and a trackable status lifecycle.
Payouts
Payouts let you disburse funds through supported rails using either:
- a previously saved payment method
- or recipient details sent in the request
Webhooks
Webhook endpoints are the preferred way to receive final or asynchronous state changes. In production, they should be treated as the source of truth for reconciliation flows.
KYC and Limits
Your KYC status affects onboarding readiness, allowed limits, and which operations can move safely into production.
Suggested Reading Path
Quick Start
Build the shortest credible integration path first.
Authentication
Secure your requests before wiring business logic.
API Overview
Understand resource structure, envelopes, and endpoint families.
Webhooks
Design around asynchronous delivery and retries from day one.
First Questions Teams Usually Need Answered
How is this guide?