This page explains the security boundary, order sync, callback verification, exception handling and customer precautions for PayPal, Antom and other payment providers.
Payment notifications are verified and duplicate handling is guarded by transaction, order and status data.
Success, failure, cancellation and delivery status are synced to orders or operating records.
Sensitive credentials such as card numbers, wallet accounts, passwords and security codes are processed by provider pages, SDKs or APIs.
Aisoft AI receives only transaction results, transaction IDs, status, amount, currency, payer email or necessary risk data required for order and support workflows.
After a provider reports success, the system syncs transaction status to the commerce backend, creates or updates the Saleor transaction and attempts to complete the order.
If front-end redirect is interrupted, payment notifications or manual record review can still be used to complete order status and delivery handling.
Payment callbacks should pass signature verification to confirm trusted source. Duplicate notifications are handled by transaction id and order status to avoid duplicate delivery.
Failure, cancellation, pending, risk review and refund states are recorded according to provider results, and delivery may pause when needed.
Before paying, verify product, amount, currency, payee and browser address. Avoid entering payment information through unknown links or unofficial pages.
If you notice duplicate charges, successful payment without order update, amount mismatch or suspected fraud, keep screenshots and transaction IDs and contact us quickly.
Refunds are reviewed with order, delivery, license and service progress, then executed through the payment provider or another mutually confirmed method.
Chargebacks, disputes, risk reviews or suspected abuse may pause delivery until payment status and ownership are clarified.