After payment

Refunds

Refunds in Feennex depend on the payment method. Detailed information will be provided by your manager.

Incorrect payment amount

Note: The payer can specify an incorrect amount only when using the bank transfer payment method.

If the payer transfers an incorrect amount, the payment status changes to recalculated. This status is final and unchangeable. Feennex sends you a notification about the payment status change to recalculated.

In the received notification and when requesting payment status, the actual amount transferred by the payer is returned in the client_price parameter. The initial payment amount is returned in the shop_original_amount parameter.

Your actions vary based on whether or not the payer has transferred enough money for the payment.

Insufficient payment

Create a new order for the missing amount. If it doesn't meet the minimum limit, accept payment from the payer using another method.

Overpayment

You need to arrange with the payer how you will compensate for the overpaid amount.

Payer made payment via bank transfer, but status remains unchanged

Note: Only for bank transfer payment method.

If the payer has made a payment via bank transfer but the payment status remains unchanged, they should have the option to send a receipt with information about the transfer.

You can implement a page for uploading the receipt and send the receipt to Feennex via API, or use a ready-made form for sending the receipt.

Step 1. Implement receipt upload page

Note: If you don't want to implement your own receipt upload page, proceed to step 2.

On the receipt upload page, it is recommended to inform the payer that the size of the image cannot exceed 10 MB, and the receipt should clearly display the following information:

• Transfer time
• Sender and recipient of the transfer
• Transfer amount

Example page for uploading receipts

Note: For each payment, the payer can only submit one receipt. Supported formats: JPEG, JPG, PNG, PDF, WebP, HEIF.

Step 2. Request payment status

To work with receipts, you need to obtain the value of the id parameter, which is unique for each payment. To get this value, request the payment status. The response returns the following parameters in the ps_data object:

• receipt_url – URL for uploading a receipt via API
• receipt_status_url – URL for checking the status of a receipt via API
• receipt_web – URL for uploading a receipt via a form. You should redirect the payer to this address if you don't want to implement the receipt upload form yourself

Example of the receipt_url parameter

"receipt_url": "https://<baseURL>/api/v1/order/ade32e06-6fa4-425a-9c4c-e026ac6d93e6/receipt"

In this parameter, https://<baseURL>/api/v1/order/ is the URL for sending requests to upload a receipt. The ade32e06-6fa4-425a-9c4c-e026ac6d93e6 string is the value of the id parameter.

Step 3. Send receipt to Feennex

Only for those who have implemented the receipt upload page (step 1).

Use the Send receipts endpoint to send a receipt that payers uploaded to Feennex. You don't need to generate signature for this endpoint.

The address to send the request to and the value of the id parameter are obtained at step 2 in the receipt_url parameter.

Example request

curl -X POST \ 
--location 'https://<baseURL>/api/v1/order/ade32e06-6fa4-425a-9c4c-e026ac6d93e6/receipt' \
--form 'file=@"/home/cwm/Pictures/receipt.jpg"'

If you successfully send the receipt, the response will have an HTTP status code of 202.

Example successful response

null

Once you send the request, Feennex's technical support processes the transfer.

To make sure that the transfer is successful, periodically send requests to request payment status.

Step 4. Display receipt status information

Note: This step is optional.

Request receipt verification status and display it on your payment page. To do this, use the Check receipt status endpoint. No signature is required for this endpoint.

To request the receipt status, you need the address to send the request and the value of the id parameter. You obtained these values in step 2 in the receipt_status_url parameter.

Example request

curl -X GET \ 
--location 'https://<baseURL>/api/v1/order/ade32e06-6fa4-425a-9c4c-e026ac6d93e6/receipt/status' \

In the response, you receive the receipt identifier, receipt status, and a comment from Feennex's technical support.

Example of a successful response

[
    {
        "id": "c9e35f42-62de-45c4-8092-152ba47d81e5",
        "status": "pending",
        "comment": null
    }
]

Once the status changes to succeed, it means that the receipt has been accepted. Make sure that the payment is completed: periodically request payment status.

Failed payment

In the payment process, issues may occur, such as payment creation failures or bank unavailability. Feennex provides a payment object with the status parameter to help understand what happened with the payment.

Use the status to determine the payment's state and use this data for analysis, communicating with the payer, or other purposes.

Learn more about statuses for failed transfers

Registers

Feennex generates registers for successful transactions, useful for reconciling accounts. These registers include the following types of operations:

• Accepted payments
• Completed payouts
• Service operations

Feennex collects information on all transactions for the day — from 00:00:00 to 23:59:59 UTC+3.

You can request reports for one day, one week, or one month.

In your personal account, within the History section, you have the option to independently generate registers for specific shops. Alternatively, if you wish to receive registers periodically via email, you can subscribe to this service.

Subscription to register distribution

To receive notifications from Feennex by email, provide the following information to your manager:

• Email addresses of recipients
• Names of the shops for which registers need to be sent
• Period for which the register should be generated – day, week, or month

The format of the register file is XSL. If there were no operations for the specified date, Feennex will send you an empty register.

Fields in the register

Field in the register	Description
Creation date	Date of the operation
Operation ID	Unique identifier of the payment, payout, or service operation
Shop ID	Identifier of your shop in Feennex
Credited to the shop	Actual amount credited to your shop, taking into account commissions. Only for payments
Debited from the shop	Actual amount debited from your shop for payouts or service operations. Includes Feennex commission
Currency	Currency of the payment – the value of the currency parameter from the payment creation request for wallet payment or shop_currency from the payment creation request for third-party payment methods. Possible currency values
Operation type	Type of the operation being performed. Possible values: Payments, Payouts, Service
Invoice amount	Payment amount – the value of the amount parameter from the payment creation request for wallet payment or shop_amount from the payment creation request for other payment methods
Invoice currency	Currency of the payment direction. Possible currency values
Payer amount	Payment or payout amount, including commission. Only for payouts. Possible currency values
Payer currency	Currency of the direction for payout. Only for payouts. Possible currency values
Order number	Order number on your side
Description	Operation description – the value of the description parameter from the payment creation request for wallet payment and other payment methods
Balance	Current balance of your shop after the operation is performed
Project ID	Service parameter. The parameter isn't used
Fee	Commission amount for payment or payout

Example of a register

"Creation date" "Operation ID" "Shop ID" "Invoice amount" "Debited from the shop" "Currency" "Operation type" "Invoice amount" "Invoice currency" "Payer amount" 
"Payer currency" "Order number" "Description" "Balance" "Project ID" "Fee"
2024-04-19 17:07:43 50000000 1234 282,94 840 Payments 301 840 i171e2d956-d3b4-457d-a26a-52d960 i171e2d956-d3b4-457d-a26a-52d960 9393,74 18,06