Payment Initialization
Payment initialization is the first step in processing any payment through the Juice API. This guide covers the core concepts, supported payment methods, and common parameters required for initializing payments.
Overview
Before capturing a payment, you must first initialize a payment session with customer and transaction details. The initialization process:
-
Validates the payment request
-
Creates a session identifier
-
Sets up the appropriate payment flow
-
Returns payment session details
Supported Payment Methods
Cards
Credit and Debit cards[Visa & Mastercard]
Bank Transfers
Direct bank transfers.
-
NGN bank accounts.
-
International wires.
-
ACH transfers.
Stablecoins
Cryptocurrency Stablecoins
Binance Pay
Direct Binance integration.
-
Multiple currencies.
-
Instant settlement.
Interac e-Transfer
Canadian bank transfers via Interac.
-
Email money transfer.
-
Instant deposits.
Mobile Money
Coming soon!
-
Multiple providers.
-
Regional support.
Universal Parameters
These parameters are required for all payment initializations regardless of the payment method:
Payment amount in minor units (e.g., cents, kobo)
-
Minimum: 100
-
Must be positive integer
-
Example: 10000 = $100.00 USD
Three-letter ISO currency code
-
Supported: NGN, USD, CAD
-
Must match payment method
-
Example: “USD”
Customer information object
Payment description
-
Maximum length: 200 characters
-
Will appear on statements
Unique transaction reference
-
Must be unique per transaction
-
Maximum length: 50 characters
Payment method details
-
Type required
-
Additional fields vary by method
Optional additional data
-
Maximum size: 10KB
-
Nested objects allowed
Required Headers
| Header | Description | Example |
|---|---|---|
| Authorization | Your API key | Bearer sk_test_abc123... |
| Content-Type | Request content type | application/json |
Never expose your API key in client-side code. Always make API calls from your server.
Basic Flow
Initialize Payment
Create payment session with customer and transaction details
Handle Authentication
Complete any required authentication steps (3DS, OTP, etc.)
Capture Payment
Finalize the payment after successful authentication
Handle Response
Process success/failure and update your system
Method-Specific Guides
For detailed implementation steps for each payment method, see:
Need Help?
-
See our
-
Contact