Search Overlay

Webhooks

Payment Handle

  1. PAYMENT_HANDLE_PAYABLE - This webhook notifies that the payment handle token created for the required purpose and it can be executed when the preliminary requirements are completed, the next API call with the payment handle can be done.

  2. PAYMENT_HANDLE_PROCESSING - This webhook is triggered when the user is successfully redirected to the payment platform page and operation has started for the payment by the user.

  3. PAYMENT_HANDLE_COMPLETED - This webhook is triggered when the process of the payment handle token is completed after triggering the next API i.e. Payments or Standalone Credit API.

  4. PAYMENT_HANDLE_EXPIRED - This webhook is triggered when the next step is not initiated after the payment handle is created within the given time frame, the duration can be seen in the response to/paymenthub/v1/paymenthandles API under the tag timeToLiveSeconds.

  5. PAYMENT_HANDLE_FAILED - This webhook is triggered when the user is successfully redirected to the payment platform page but some technical error occurred and final communication couldn't reach back to Paysafe.

Payments

  1. PAYMENT_PROCESSING: The payment is in progress. In some cases, there might be delays due to an action pending by the customer or the merchant.

  2. PAYMENT_PENDING- The payment is pending because the transaction hasn't been completed from the bank account to Skrill wallet to merchant.

  3. PAYMENT_COMPLETED/SETTLEMENT_COMPLETED - The payment was completed successfully.

  4. PAYMENT_FAILED - This webhook is triggered when the payment fails during the process.

Standalone Credits/Withdrawal

  1. SA_CREDIT_FAILED - This webhook is triggered in case the transaction was initially completed and later failed due to some settlement error.

  2. SA_CREDIT_CANCELLED - This webhook is triggered when the transaction was canceled after it was completed.

  3. SA_CREDIT_ERRORED - This webhook is used when there is a technical error during the initiation of a transaction.

  4. SA_CREDIT_PENDING - This webhook is triggered when the withdrawal has been initiated but due to various bank delay reasons or time zone issues the actual money transfer has not happened.

Refunds

  1. REFUND_FAILED - This webhook is triggered when the refund is initiated but failed due to a functional error.

    Example - refund amount is more than the Payment amount.

  2. REFUND_COMPLETED - This webhook is triggered when the refund has been successfully transferred from merchant account to the user's chosen bank account

  3. REFUND_PENDING - This webhook is triggered when refund has been initiated but due to various bank delay reasons or time zone issues the actual money transfer has not happened.

On this Page