Create a payment request
Create a payment request for the client for a specified amount and a configurable expiration time.
url_store field uses the secure HTTPS protocol, uses domain names (not IP addresses) and is considered clean by VirusTotal and similar scanners.Headers
Hex-encoded HMAC-SHA512 signature of the request body, generated using your secret key.
Body
Payment request amount that you want to receive from the customer.
"100.50"
The currency you want to receive.
Payment request lifetime (duration in seconds). Include either this parameter or life_time_datetime. At least one of these fields is required.
3600
Payment request lifetime (exact expiry timestamp). Include either this parameter or life_time_duration. At least one of these fields is required.
1773768946
The currency your customer will pay in. You can set both the currency and network or just the currency.
If the amount the customer pays does not match the amount that you set for the payment request, CryptoProcessing will send an email to this address instructing the customer on how they can receive a refund. If they paid less, they will receive a full refund. If they paid more, the customer will get instructions on how to be refunded the difference.
The unique ID of the customer this payment request is for. You can use it to group payment requests by customer.
Type of the merchant's customer who sends the funds.
Use natural if the sender is an individual person and legal if the sender is a legal entity. The selected type determines which fields must be included in sender_data.
natural, legal Required if sender_type is provided. Must contain the details of the merchant's customer who sends the funds.
- If
sender_typeisnatural, includefirst_name,last_name, and optionallydate_of_birth. Do not includelegal_nameorcountry_of_registration. - If
sender_typeislegal, includelegal_nameandcountry_of_registration. Do not includefirst_name,last_name, ordate_of_birth.
Payment request description that the customer will see.
"Order #123"
Unique foreign ID in your system. Must not contain personal data, such as the user's name or email address.
"order_123"
URL of the store page. The customer can click a button on the payment form to return to this URL (for example, if they change their mind or want to pick a different payment method). We recommend setting this to the URL of the checkout page.
"example.com/store"
URL of the success page. The customer will be able to return to this address once the payment is completed.
"example.com/success"
URL of the failed payment page. The customer will be able to return to this address if the payment fails.
"example.com/fail"
Response
OK