P2P API

Use the P2P API for peer-to-peer payment flows.

Detailed Documentation: https://api.blikk.tech/p2papi/docs

Service Purpose

The P2P API enables creation and management of peer-to-peer payments between users, supporting both immediate and deferred flows.

Contact

For implementation help or questions, contact hello@blikk.tech

Key APIs / Endpoints

• POST /p2p: Create a P2P payment with one creditor and one debtor.
• POST /p2p/creditor: Create a P2P payment with one creditor and a debtor to be completed later.
• GET /payment/{id}: Fetch a payment by ID.
• POST /payment/init/{id}: Initialize a payment for account-to-account flow.

Architecture Overview

TBD — Architecture diagram and flow description not present in repo.

Dependencies

TBD — Upstream dependencies and integrations not documented in repo.

Getting Started

1. Obtain an API key from Blikk.
2. Use HTTPS endpoints.
3. Include the Api-Key header in every request.

Authentication

All endpoints require the Api-Key HTTP header:

Api-Key: <your-api-key>

Error Cases

HTTP Status	Cause
401 Unauthorized	Missing or invalid Api-Key
400 Bad Request	Invalid request payload or validation
404 Not Found	Referenced payment does not exist
5xx	Temporary server or dependency failure

Implementation Tips

• Always send Api-Key in headers.
• Use E.164-like phone input when available.
• Treat amount as a numeric value in minor units only when confirmed by product requirements.
• Treat expiresAt as a Unix timestamp (seconds).
• Store and reuse returned payment id for follow-up calls.
• On transient failures (5xx), retry with bounded exponential backoff.

Security Notes

• Use test keys and test data in non-production environments.
• Redact API keys, tokens, phone numbers, and identifiers in diagnostics.
• Keep logs and traces free of full credential values.

Glossary

TBD — Glossary not present in repo.

Support

Contact hello@blikk.tech for support.