API
HomeEasytransac
HomeEasytransac
  1. Documentation
  • Start
    • API Domain Usage
    • Get an API key
    • Communication
  • Documentation
    • Errors
      • ApiError codes
    • Webhooks
      • PUSH Method
      • PULL Method
  • V2
    • Overview
    • Authentication
      • JWT access token - Generate
        POST
    • Endpoints
      • Open Banking
        • Open Banking - Initialize
      • SDD
        • SDD - Mandate - Create
        • SDD - Mandate - Debit
        • SDD - Mandate - Get status
      • Transaction
        • Transaction - Get status
  • V1
    • Documentation
      • Signature
    • Authentication
      • Overview
      • Security
      • PSD2 and 3DSecure
    • API - Payment
      • Recurring payments
      • Card payment
      • 1-click payment
      • SEPA Direct Debit
      • Transfer (Open Banking)
      • Payment page
      • Cancel a payment page
      • Resend the payment page
      • P2P Transfert
      • Update a subscription
      • Status
      • Refund
      • Capture
      • Cancellation
      • List of cards
      • List of IBANs
      • History
      • Payment requests
      • Card information
    • API - User
      • Add a merchant
      • Update a merchant
      • Search for a merchant
      • List of movements
      • Make a payout
      • List all payouts
      • Add a logo
      • Get the activity
      • Update activity
    • API - Document
      • Add a document
      • Get a document
      • List documents
  1. Documentation

Webhooks

The notification process (webhook) has been developed to add real-time monitoring of your transactions. Thanks to our notifications, you can follow your transactions and react to all events:
New transaction.
Refund
Chargeback
Adding a card
SEPA transfer
Status of a sub-account
Document status (KYC)
INFO
The notification is sent with the POST method via the HTTP protocol. For a transaction-related webhook, the parameters are identical to the response of a card payment.
NOTE
During a transaction, you may receive multiple notifications with different Status corresponding to the status of the payment during its cycle. Be careful to credit your customers only once if you receive multiple notifications with the status "captured".
If a 3DSecure transaction is not completed, it will automatically expire after 20 minutes. You will then receive a notification with a status "failed".
PUSH notifications are recommended as they can be applied more generally without overloading the network.
Previous
ApiError codes
Next
PUSH Method
Built with