Webhook Operation Types

EdfaPay provides webhook callbacks for the following operation types, correlating with various payment workflows:

Operation Type	Description
SALE	Indicates a payment (sale) transaction is being processed.
3DS	Signifies that a 3D Secure authentication process is initiated or ongoing.
REDIRECT	Occurs when the customer is redirected for an additional action (e.g., 3D Secure authentication).
REFUND	Denotes that a refund request has been processed.
RECURRING	Represents a recurring payment initiated using stored credentials or a token.

API Request Actions

When submitting API requests to EdfaPay, specify the action parameter corresponding to the desired transaction type:

Action	Description
Initiate	Creates a SALE (payment) or AUTH (authorization) transaction.
Refund	Initiates a refund for an existing transaction.
STATUS	Retrieves the current status of a transaction.
Recurring	Creates a SALE or AUTH using previously stored customer card data.

Transaction Result and Status Values

This section details the possible Result and Status values returned for transactions.

Result — Immediate Outcome of the Action

The Result indicates the immediate outcome of the performed action.

Result	Description
SUCCESS	The action was successfully completed.
DECLINED	The action failed or the transaction was rejected.
REDIRECT	An additional action is required, typically a 3D Secure redirection.
ACCEPTED	The request was accepted, but processing will complete at a later time.
ERROR	The request contained errors or was invalid.

Status — Current Lifecycle State of the Transaction

The Status reflects the current lifecycle state of the transaction.

Status	Description
3DS	Transaction is awaiting 3D Secure authentication (Challenge).
REDIRECT	Transaction is awaiting customer redirection (e.g., to a 3D Secure page).
SETTLED	Payment completed successfully, and funds have been captured.
REFUND	Payment has been successfully refunded.
DECLINED	Payment failed or the transaction was rejected.

Important Notes

EdfaPay webhook notifications are asynchronous; always verify transaction status via direct API calls. Properly manage REDIRECT and 3DS flows requiring customer interaction. Distinguish between 'Result' (immediate API outcome) and 'Status' (transaction lifecycle state); a successful 'Result' doesn't guarantee finalization. Implement idempotency checks for webhook processing.

Security Considerations

Always verify webhook digital signatures. Configure webhook endpoints securely with HTTPS and enforce strict access controls. Adhere to PCI DSS for sensitive cardholder data. Implement robust error handling and logging, avoiding exposure of sensitive information. Handle and store customer card data securely, compliant with best practices and regulations.