Braintree payment integration for ecommerce

iWeb sends authorisation at checkout and capture when order is confirmed. This means payment is not taken until inventory is reserved and fraud checks pass. If order is cancelled before confirmation, the authorisation is voided and the shopper is not charged.

Braintree returns a decline code to commerce. iWeb logs the decline reason (insufficient funds, card expired, velocity limit, etc.) and displays a message to the shopper. The shopper can retry with a different payment method without creating a new order record.

iWeb sends the refund instruction to Braintree with the original transaction ID. Braintree credits the cardholder or PayPal account, and iWeb logs the refund as reconciled once ERP posts the corresponding credit note. The customer sees the refund in their bank or PayPal account within 1-3 business days.

Yes. iWeb manages Braintree's customer vault so repeat customers can check out by selecting a saved card without re-entering details. The shopper must consent to storage; iWeb enforces consent capture and can delete stored methods on request or if a card is compromised.

iWeb enforces 3D Secure enrollment checks and sends the required nonce or lookup result to Braintree. For SCA step-up, iWeb receives the challenge URL from Braintree, redirects the shopper to authenticate, and completes the payment only after successful challenge.

iWeb implements timeouts and fallback logic. If Braintree API is unreachable, checkout can either queue the authorisation for retry or decline the transaction with a customer-facing message. Post-launch, iWeb monitors Braintree API availability and alerts operations if degradation exceeds thresholds.

iWeb extracts Braintree settlement files daily, maps payment methods and schemes to ERP nominal codes, and posts batched or line-level journal entries to the ledger. Each settlement batch is tagged with the Braintree batch ID so finance can audit back to Braintree if amounts mismatch.

iWeb queues the failed refund and retries it per the configured policy. If the refund is not refundable to the original method, iWeb alerts finance and routes the refund to a fallback method (e.g. store credit or manual bank transfer). ERP credit note is held pending final refund resolution.

iWeb implements idempotency keys on all Braintree requests (auth, capture, refund) and deduplicates incoming webhooks by Braintree transaction ID and timestamp. If the same transaction is submitted twice, iWeb returns the cached result instead of submitting to Braintree again.

iWeb logs all Braintree chargeback webhooks and queues them for dispute workflow. Customer service, finance and returns teams are notified immediately. iWeb tracks chargeback status (won, lost, pending) and can trigger return requests or account adjustments based on chargeback outcome.

Yes. iWeb manages token refresh on subscription renewal, handles failed payment retries with exponential backoff, and sequences billing events into your order and invoice systems. Braintree does not own the subscription calendar; iWeb manages renewal timing based on your subscription rules.

iWeb sends the transaction amount and currency code to Braintree, which processes the payment in that currency. Settlement is converted to your base currency by Braintree's processor. iWeb maps FX variance and scheme fees to separate ERP nominal codes so you can track hedging and settlement cost.

iWeb logs every authorisation request, response code, capture instruction, refund and webhook delivery to a secure audit trail. Logs capture shopper details (masked card, email), amounts, timestamps, Braintree transaction IDs and decision codes. Finance and compliance can retrieve logs for transaction disputes and reconciliation.

iWeb runs sandbox parity testing, validates 3D Secure enrollment and SCA flow, tests refund and chargeback webhook delivery, confirms ERP reconciliation on batched settlements, and executes a rollback plan if Braintree must be swapped for another gateway. Pre-launch checklists cover data format, timeout handling and exception routing.