Callbacks

After Epoint processes a payment and receives the bank’s response, the payment details are sent to your server via a POST request to your result_url.

Callback Flow

Epoint sends data and signature parameters via POST to your result_url
Your server verifies the signature to ensure the response is authentic
Your server decodes the data to get payment details

Verifying the Callback

To verify the callback is genuinely from Epoint:

Generate signature on your server using the received data and your private_key:

Encode & Sign

1signature = base64_encode(sha1(private_key + data + private_key, 1))

Compare the generated signature with the signature received from Epoint
If they match, the response is authentic and has not been tampered with
Decode the data:

Encode & Sign

1result = json_decode(base64_decode(data))

Callback Response Parameters

Parameter	Description
`order_id`	Unique order ID from your application
`status`	Transaction result: `success` or `failed`
`code`	Bank response code
`message`	Payment status message
`transaction`	Epoint transaction identifier
`bank_transaction`	Bank transaction identifier
`bank_response`	Bank response for the payment
`operation_code`	`001` — card registration, `100` — customer payment
`rrn`	Retrieval Reference Number — unique identifier (only for successful transactions)
`card_name`	Cardholder name shown on payment page
`card_mask`	Card mask in `123456******1234` format
`amount`	Payment amount
`other_attr`	Additional parameters
`trace_id`	Unique request identifier for debugging and support

Payment Statuses

Status	Description
`new`	Payment registered in Epoint system
`success`	Payment completed successfully
`returned`	Payment refund was processed
`failed`	An error occurred during payment
`error`	An error occurred during payment
`server_error`	Status verification error

Status Check API

You can check the payment status at any time using the Get Status API endpoint.