v1.0.2 (Latest)

⚠️ Important

In rare cases, a P2P deposit previously marked as fail may later be confirmed as success by the banking provider within 24 hours.

In such situations:

The system may send a new webhook for the same paymentId with status success

This should be treated as a valid status update, not just a duplicate webhook

If the payment was previously stored as fail, it should be updated to success

This behavior is separate from regular webhook retry attempts.

v1.0.1 (Latest)

🚀 Added

CreatePaymentResponseDto now includes new fields:

amountToChargeInCents (required)

cardNumber (optional)

⚠️ Changed

amountToChargeInCents is now a required field in the response.

This field represents the final amount the user must pay, including commissions or provider-specific adjustments.

For P2P payment type, the API may also return:

cardNumber — recipient card number for completing the transaction

📦 Updated Response Schema

`CreatePaymentResponseDto`

{
  "data": {
    "paymentId": "43066701-0111-412c-8a0c-b8c06800449d",
    "status": "new",
    "amountInCents": 10050,
    "amountToChargeInCents": 10200,
    "currencyId": "UAH",
    "paymentUrl": "https://pay.xbit.com/...",
    "cardNumber": "444111****2222"
  }
}

Changelog

v1.0.2 (Latest)#

⚠️ Important#

v1.0.1 (Latest)#

🚀 Added#

⚠️ Changed#

📦 Updated Response Schema#