Wix Velo Technical Specification: Custom Payment Options & Cash on Delivery (COD) Handling fee via SPI
Budget: $30 – $250 USD
Project: gumikesztyu-shop.hu (Wix E-commerce platform)
Objective: Split the single default Wix Manual/Offline Payment method into two separate, dedicated options on the Checkout page, and implement an automatic handling fee calculation for Cash on Delivery.
1. Functional Requirements (Checkout Page UX)
Instead of the single default Wix Manual Payment radio button, the customer must see and be able to select from two distinct, independent options within the payment section:
Option A: „Banki átutalás (gazdasági társaságoknak, cégeknek, intézményeknek)”
Option B: „Utánvétes fizetés átvételkor (+300 Ft kezelési költség)”
2. Backend Logic & Automation (Wix Custom Payment SPI / Velo)
When Option A („Banki átutalás...”) is selected:
The cart/order total must remain unchanged.
Upon successful order placement, the automated Wix Order Confirmation Email (Transactional Email) must dynamically include the merchant's bank details: Bank Name, IBAN/Account Number, and payment instructions.
The order status on the Wix Dashboard must be automatically set to: „Pending Payment”.
When Option B („Utánvétes fizetés...”) is selected:
The system must utilize the Wix Custom Payment SPI (or wix-pricing-backend) to automatically append a +300 HUF handling fee to the current order total.
This extra charge must be dynamically calculated and displayed in the Order Summary breakdown on the Checkout page before the user clicks the final "Place Order" button.
The order status on the Wix Dashboard must be automatically set to: „Not Paid” with fulfillment status set to „Ready for Shipping”.
3. Technical & Implementation Requirements
Architecture: The developer must implement this using the Wix Studio / Wix Velo Custom Payment SPI (Service Provider Interface) framework to ensure secure and seamless integration with the native Wix Checkout block.
Compatibility: The code must be robust, fully responsive (optimized for both desktop and mobile viewports), and must not cause any lag or freezing during the checkout session.
Localization: String constants displayed to the end-user must precisely match the Hungarian labels provided in Section 1.
Objective: Split the single default Wix Manual/Offline Payment method into two separate, dedicated options on the Checkout page, and implement an automatic handling fee calculation for Cash on Delivery.
1. Functional Requirements (Checkout Page UX)
Instead of the single default Wix Manual Payment radio button, the customer must see and be able to select from two distinct, independent options within the payment section:
Option A: „Banki átutalás (gazdasági társaságoknak, cégeknek, intézményeknek)”
Option B: „Utánvétes fizetés átvételkor (+300 Ft kezelési költség)”
2. Backend Logic & Automation (Wix Custom Payment SPI / Velo)
When Option A („Banki átutalás...”) is selected:
The cart/order total must remain unchanged.
Upon successful order placement, the automated Wix Order Confirmation Email (Transactional Email) must dynamically include the merchant's bank details: Bank Name, IBAN/Account Number, and payment instructions.
The order status on the Wix Dashboard must be automatically set to: „Pending Payment”.
When Option B („Utánvétes fizetés...”) is selected:
The system must utilize the Wix Custom Payment SPI (or wix-pricing-backend) to automatically append a +300 HUF handling fee to the current order total.
This extra charge must be dynamically calculated and displayed in the Order Summary breakdown on the Checkout page before the user clicks the final "Place Order" button.
The order status on the Wix Dashboard must be automatically set to: „Not Paid” with fulfillment status set to „Ready for Shipping”.
3. Technical & Implementation Requirements
Architecture: The developer must implement this using the Wix Studio / Wix Velo Custom Payment SPI (Service Provider Interface) framework to ensure secure and seamless integration with the native Wix Checkout block.
Compatibility: The code must be robust, fully responsive (optimized for both desktop and mobile viewports), and must not cause any lag or freezing during the checkout session.
Localization: String constants displayed to the end-user must precisely match the Hungarian labels provided in Section 1.