WooCommerce Plugin for On-Site Stripe Payment Routing with Multi-Account Load Balancing
Budget: $30 – $250 USD
We are running a WooCommerce website that sells custom digital packages and are looking for a skilled developer to build a plugin that:
1.Processes Stripe payments entirely on-site using Stripe Elements or Payment Intents API (no redirects).
2.Distributes transactions across multiple Stripe accounts, based on round-robin or custom logic (e.g., per transaction, per region, per volume).
3.Sends clean and generic product metadata to Stripe (e.g., “Digital Package”, “Online Service”) regardless of the actual item being delivered.
4.Ensures the actual order confirmation, product details, and delivery info are handled only via our main website and email system — not exposed through Stripe.
5.Supports routing transactions via a proxy or secondary site/server, so that our primary website and server IP remain fully isolated from what Stripe sees.
Requirements:
•Custom WooCommerce plugin or extension
•PCI-compliant Stripe API usage (Elements, Payment Intents)
•Configurable list of multiple Stripe keys/accounts with logic control
•Optional proxy mechanism for externalized payment context
•Clean codebase, modular, and maintainable
Important Notes:
•We sell legitimate digital goods and follow all applicable laws.
•The goal is to create a robust, flexible architecture for managing payments across multiple merchant accounts while maintaining privacy, brand control, and consistent customer experience.
1.Processes Stripe payments entirely on-site using Stripe Elements or Payment Intents API (no redirects).
2.Distributes transactions across multiple Stripe accounts, based on round-robin or custom logic (e.g., per transaction, per region, per volume).
3.Sends clean and generic product metadata to Stripe (e.g., “Digital Package”, “Online Service”) regardless of the actual item being delivered.
4.Ensures the actual order confirmation, product details, and delivery info are handled only via our main website and email system — not exposed through Stripe.
5.Supports routing transactions via a proxy or secondary site/server, so that our primary website and server IP remain fully isolated from what Stripe sees.
Requirements:
•Custom WooCommerce plugin or extension
•PCI-compliant Stripe API usage (Elements, Payment Intents)
•Configurable list of multiple Stripe keys/accounts with logic control
•Optional proxy mechanism for externalized payment context
•Clean codebase, modular, and maintainable
Important Notes:
•We sell legitimate digital goods and follow all applicable laws.
•The goal is to create a robust, flexible architecture for managing payments across multiple merchant accounts while maintaining privacy, brand control, and consistent customer experience.