Apple Pay button not showing in HyperPay paymentWidgets on Safari (Odoo backend)

by

Summary

The Apple Pay button is not visible in HyperPay paymentWidgets on Safari despite a clean test HTML page and proper setup. The issue persists even after verifying Apple Pay and domain verification.

Root Cause

The root cause of this issue can be attributed to several factors, including:

  • Incorrect configuration of HyperPay or Apple Pay
  • Insufficient setup on the Odoo backend
  • Incompatibility issues with Safari or iOS
  • Missing requirements for Apple Pay to function properly

Why This Happens in Real Systems

This issue occurs in real systems due to:

  • Complexity of payment gateway integrations
  • Variations in browser and device support
  • Stringent security requirements for Apple Pay
  • Interdependencies between HyperPay, Apple Pay, and Odoo

Real-World Impact

The impact of this issue includes:

  • Loss of sales due to inaccessible payment options
  • Negative user experience resulting from blank or unresponsive pages
  • Increased support requests and technical issues
  • Damage to brand reputation due to perceived instability

Example or Code

var wpwlOptions = {
  paymentTarget: "_top",
  locale: "en",
  applePay: {
    displayName: "MyStore",
    total: { label: "MyStore" },
    supportedNetworks: ["visa", "masterCard", "mada"]
  },
  onError: function (error) {
    document.body.innerHTML = "
" + JSON.stringify(error, null, 2) + "


";

  }

};


How Senior Engineers Fix It


Senior engineers fix this issue by:


    

  • Verifying HyperPay and Apple Pay configurations
    • 

  • Checking Odoo backend setup and compatibility
    • 

  • Testing on multiple devices and browsers
    • 

  • Ensuring all security and requirements are met
    • 

  • Debugging JavaScript errors and exceptions
    • 



Why Juniors Miss It


Junior engineers may miss this issue due to:


    

  • Lack of experience with payment gateway integrations
    • 

  • Insufficient knowledge of Apple Pay requirements
    • 

  • Inadequate testing on various devices and browsers
    • 

  • Overlooking critical configuration details
    •

Leave a Comment