Crypto
Crypto Pay-In API
This guide explains how to integrate with The Payment Company Crypto Payin API. The API supports seamless cryptocurrency payment processing and includes endpoint details, payload information, and examples in multiple programming languages.
API Endpoint
https://api.thepayment.company/api/v1/live/crypto/payinhttps://api.thepayment.company/api/v1/test/crypto/payinRequest Fields
| Parameter | Type | Description | Required |
|---|---|---|---|
first_name | String | Payer first name | Yes |
last_name | String | Payer last name | Yes |
email | String | User email address | Yes |
amount | Number | Transaction amount in the smallest currency unit | Yes |
currency | String | Currency code in ISO 4217 format | Yes |
crypto_currency | String | Cryptocurrency code, such as BTC, ETH, or USDT | Yes |
crypto_network | String | Cryptocurrency network, such as ETHEREUM or BITCOIN | Yes |
ip_address | String | User IP address | Yes |
phone_number | String | Payer phone number | Yes |
address | String | Billing street address | Yes |
country | String | Country code in ISO 3166-1 alpha-2 format | Yes |
order_id | String | Merchant-side unique order reference | Yes |
redirect_url | String | URL where the user is redirected after payment | Yes |
webhook_url | String | URL used for server-to-server webhook updates | No |
terminal_id | String | Unique connector terminal ID, useful when bypassing routing and cascading logic | No |
Payload
Send the request payload as JSON. The sample structure is shown below:
Sample Responses
Understanding Crypto Payment Status
The crypto_payment_status field in the response indicates the payment completion status for cryptocurrency transactions. It is used to determine whether the received amount exactly matches, falls below, or exceeds the requested amount.
Payment Status Values
Description: The customer paid the exact requested amount.
Implementation Notes
Important: Always check the crypto_payment_status field before fulfilling orders for cryptocurrency payments. Because of blockchain transaction characteristics, small variations in payment amounts can occur because of:
- Network fees and gas prices
- Exchange-rate fluctuations during transaction processing
- Limitations in the user's wallet
Integration Notes
Encrypted payment APIs must use AES-256-CBC before transmitting sensitive fields. Authentication, headers, encryption steps, and sample implementations for Node.js, PHP, Python, and Java are documented in Integration Examples.