BigCommerce Eway Shared Page: Custom Solutions for Card Surcharges

Unlocking Eway Shared Page: Custom Solutions for Card Surcharge Fees in BigCommerce

Many e-commerce merchants rely on robust payment gateway integrations to manage transactions efficiently. However, specific business requirements, such as implementing card-type surcharge fees, can sometimes push the boundaries of native platform integrations. A recent discussion in the BigCommerce community highlighted a common challenge faced by merchants using Eway: the limitation of BigCommerce's default Eway integration to "Direct Connection" only, preventing the implementation of card-specific surcharges.

The Challenge: Eway Direct Connection vs. Shared Page for Surcharges

The core issue raised by merchant John Shidiak was the inability to implement card surcharge fees using the standard BigCommerce + Eway integration. This functionality typically requires Eway's "Shared Page" experience, where customers are redirected to a secure Eway page to complete their payment, allowing for dynamic surcharge calculations based on the card type selected. The native BigCommerce integration, however, primarily supports "Direct Connection," which processes card details directly on the BigCommerce checkout page without the necessary redirect flow for surcharge logic.

As confirmed by community experts, this isn't a simple configuration tweak. Card-type surcharges inherently depend on the shared/redirect payment experience, making it impossible to achieve through out-of-the-box BigCommerce settings.

Community-Driven Solutions for Custom Eway Integration

Recognizing the need for a custom approach, BigCommerce partners and developers in the thread offered several viable strategies to overcome this limitation. These solutions underscore the flexibility of the BigCommerce platform and its APIs for advanced customization:

• Custom Payment Integration with Redirect: The most direct approach involves developing a custom payment gateway integration. This would entail redirecting customers to the Eway shared page for payment processing and then handling the callback from Eway back to BigCommerce to update the order status. This method allows for the pre-calculation and application of surcharges before the customer is sent to Eway.
• Checkout-Level Customization using Open Checkout: For merchants leveraging BigCommerce's Open Checkout (formerly Checkout SDK), significant customization can be achieved. This allows developers to build a highly tailored checkout experience, potentially integrating Eway's shared page logic more seamlessly within the BigCommerce environment, or even using a custom UI to capture card details and apply surcharges before interacting with Eway's API.
• Middleware Layer for Surcharge Logic: Another sophisticated approach involves introducing a light middleware layer. This external service would sit between BigCommerce and Eway, intercepting payment requests, applying the necessary surcharge logic based on card type, and then forwarding the adjusted transaction to Eway's shared page. This offers a decoupled and scalable way to manage complex payment rules.

Both Codinative.com and Arizon.digital, certified BigCommerce partners, expressed confidence in their ability to develop such custom solutions, highlighting their experience with BigCommerce's Payments API and general API integrations. They emphasized the importance of reviewing Eway's Rapid API documentation and assessing the full scope to provide accurate timelines and estimates.

Key Takeaways for BigCommerce Merchants

For BigCommerce merchants looking to implement specific card-type surcharge fees with Eway, this discussion offers crucial insights:

• Native Integration Limitations: Be aware that BigCommerce's default Eway integration supports "Direct Connection" only, which does not facilitate card-type surcharges requiring a "Shared Page" experience.
• Custom Development is Key: Achieving this functionality requires custom development, leveraging BigCommerce's powerful APIs and potentially Eway's Rapid API.
• Explore Partner Expertise: Engaging with experienced BigCommerce partners or developers is essential. They can help navigate the complexities of custom payment integrations, Open Checkout customizations, or middleware solutions to meet specific business needs.

While the native integration provides convenience, specific requirements like dynamic surcharges often necessitate a deeper dive into custom development. The BigCommerce ecosystem, supported by its flexible APIs and a network of skilled partners, is well-equipped to handle such advanced challenges, ensuring merchants can tailor their checkout experience to their unique business models.