Get started with nekuda SDKs for AI agents to handle payments securely in minutes.
https://api.nekuda.ai
.
@nekuda/react-nekuda-js
) - Securely collect payment details in your UInekuda
) - For Python applicationsnekuda
) - For Node.js/TypeScript applicationsFrontend: Collect Payment Details
@nekuda/react-nekuda-js
to securely capture credit card information from
the user and obtain a payment token or reference.Backend: Process Information
user_id
.mandate_id
obtained from mandate creation.user_id
(string) identifying your end-user must be provided when creating a user context.mandate_id
.mandate_id
is then required to request a reveal_token
.pk_live_your_public_key_here
with your actual Public Key from
the nekuda Dashboard. Never expose your Secret Key
(sk_live_...
) in frontend code. The user_id
used in the frontend SDK
provider should match the user_id
used in your backend nekuda
SDK calls
for the same user.sk_live_...
) secure on your backend. Never
expose it in client-side code or public repositories. The API endpoint
https://api.nekuda.ai
is the standard for production.Test API Keys (from app.nekuda.ai)
pk_test_...
(use this in
NekudaWalletProvider
) - Secret Key (Backend): sk_test_...
(use this
for NEKUDA_SECRET_KEY
for the Python nekuda
SDK)Test Card Details (for frontend collection)
pk_test_...
key. Refer to the sandbox/testing section in the nekuda developer
documentation or dashboard. Common test card patterns (actuals may vary, check
nekuda docs): - Visa: 4242
4242
4242
4242
- Expiry: Any future
date (e.g., 12/25
) - CVC: 123
- Name: Test User
@nekuda/react-nekuda-js
for frontend payment
collection.pk_live_...
and
sk_live_...
) obtained from app.nekuda.ai. Implement
robust error handling, logging, and monitoring for all backend processes.