Skip to main content
Find answers to common questions about integrating with and using Peere Network’s identity-based payment system.

​
General Questions

Peere Network is an identity-based payment system that allows customers to make payments using their identity (biometric data, device recognition) instead of traditional payment methods like cards or cash. It creates an “invisible economy” where transactions happen seamlessly without visible payment instruments.
Customers are identified through biometric data (palm prints, facial recognition) or linked devices. When they want to make a payment, their identity is verified and the transaction is processed through their linked bank account without needing cards, cash, or phones.
Currently, Peere Network operates in Nigeria with support for Nigerian Naira (NGN). We’re actively expanding to support USD, GBP, USDT, and other African currencies. Contact us for early access to new regions.
Yes, Peere Network uses bank-grade security including encryption, secure API authentication, webhook signature verification, and compliance with financial regulations. All transactions require customer authorization through their trusted bank.

​
Integration Questions

  1. Sign up for a Peere account at dashboard.peere.network 2. Complete KYC verification for your business 3. Get your API keys from the dashboard 4. Choose your integration path (Merchant, Bank, or Provider) 5. Follow our getting started guide
  • Sandbox: For development and testing with simulated data and transactions - Live: For production with real customers and actual money transfers Use sandbox for integration development, then switch to live after testing is complete.
Basic API integration knowledge is helpful, but we provide comprehensive documentation, code examples, and SDKs. Our support team can also assist with integration questions.
  • Basic integration: 1-2 weeks - Full integration with webhooks: 2-4 weeks - Enterprise integration: 4-8 weeks Timeline depends on complexity and your development resources.

​
Merchant Questions

You can find customers using: - Email lookup: GET /v1/customer/banks?email=customer@example.com - Device lookup: POST /v1/customer/device/lookup with device ID Customers must be onboarded by their banks to be discoverable.
  • Billing Intent: Request permission to bill a customer (establishes agreement) - Billing Request: Actually bill the customer using an approved agreement phrase You must send a billing intent first to get customer approval before billing.
Customers can set spending limits when approving billing intents: - Single: Maximum per transaction - Daily: Maximum per day - Weekly: Maximum per week - Monthly: Maximum per month You must respect these limits when billing customers.
You’ll receive a webhook notification with customerAction: "declined" and can offer alternative payment methods or retry later.

​
Bank Questions

Use the batch customer migration endpoint: bash POST /v1/bank/customers You can migrate customers in batches of 100-500. See our migration guide for details.
Banks receive: - billing.intent: When merchants want billing permission - billing.request: When merchants attempt to bill customers You respond to these webhooks after collecting customer decisions.
When customers approve billing intents, they can set spending limits. You should: - Store these limits in your system - Validate transactions against limits - Auto-approve within limits or request customer approval

​
Provider Questions

Use the batch merchant creation endpoint: bash POST /v1/provider/merchants After creation, set appropriate trust levels for each merchant.
  • Basic: Standard billing operations - Enhanced: Device lookup + advanced billing - Premium: Full feature access + priority support Higher trust levels unlock more capabilities for merchants.
Yes, providers can perform all billing operations on behalf of their merchants using the merchant’s entityId in API calls.
Peere handles settlements automatically. You can track settlement status and manage merchant balances through the API and dashboard.

​
Technical Questions

Peere uses Bearer token authentication. Include your API key in the Authorization header: Authorization: Bearer YOUR_API_KEY
Use HMAC SHA-256 to verify webhook signatures: javascript const expectedSignature = crypto .createHmac('sha256', webhookSecret) .update(payload) .digest('hex');
Rate limits vary by endpoint and account type. Monitor these headers: - X-RateLimit-Limit: Total requests allowed - X-RateLimit-Remaining: Requests remaining - X-RateLimit-Reset: When limit resets
Peere uses standard HTTP status codes: - 2xx: Success - 4xx: Client errors (fix your request) - 5xx: Server errors (retry with backoff) See our status codes guide for details.

​
Webhook Questions

For Merchants: - billing.intent.response: Customer decision on billing authorization - billing.response: Payment confirmation from bank For Banks: - billing.intent: Merchant wants billing authorization - billing.request: Merchant wants to bill customer
  1. Create HTTPS endpoints in your application 2. Configure webhook URLs in the Peere dashboard 3. Verify webhook signatures for security 4. Return 200 status code for successful processing
Peere automatically retries failed webhooks with exponential backoff. You can also manually replay webhooks from the dashboard.
Use the webhook testing tools in the sandbox dashboard or create test webhooks using our API examples in the documentation.

​
Business Questions

Peere charges processing fees based on transaction volume and account type. Contact sales@peere.network for detailed pricing information.
- Nigeria: T+1 (next business day) - Other regions: Varies by local banking systems Settlement times may vary during holidays or system maintenance.
Yes, merchants can initiate refunds using: bash POST /v1/refunds/initiate Refunds typically process within 1-3 business days.
Minimum amounts vary by currency: - NGN: ₦1.00 - USD: $0.01 (when available) - GBP: £0.01 (when available)

​
Troubleshooting

Possible causes: - Customer not onboarded by their bank - Incorrect email or device ID - Customer’s bank not integrated with Peere Solutions: - Verify customer information - Check if customer’s bank supports Peere - Offer alternative payment methods
Possible causes: - Incorrect webhook URL configuration - Endpoint returning non-200 status codes - SSL certificate issues Solutions: - Verify webhook URL in dashboard - Check endpoint logs for errors - Ensure HTTPS with valid SSL certificate
Possible causes: - Invalid or expired API key - Missing Authorization header - Using wrong environment API key Solutions: - Verify API key is correct - Check Authorization header format - Ensure using correct environment key
Possible causes: - Transaction amount exceeds customer limits - Daily/monthly spending limits reached Solutions: - Check customer spending limits - Request customer to approve higher amount - Split transaction into smaller amounts

​
Support and Resources

Documentation

Comprehensive integration guides and API reference

Dashboard

Manage your integration and monitor transactions

Support

Get help from our technical support team

Status Page

Monitor system status and planned maintenance

​
Still Have Questions?

Contact Our Team

Can’t find the answer you’re looking for? Our team is here to help! - Technical Support: support@peere.network - Sales Inquiries: sales@peere.network - Partnership: partnerships@peere.network - General: hello@peere.network