Fix Event Ticketing Payment Calculations on WordPress Site
Budget: $30 – $250 USD
I need an experienced Full Stack Software Developer to address incorrect payment calculations in my multi-vendor event ticketing system.
// KEY DETAILS //
**Issue with Current Payment System:** The current payment solution is not calculating payments accurately. This issue needs to be resolved promptly.
// OBJECTIVE //
The objective of this project is to edit our code for our payment solution so it will calculate the correct Service Fee and Processing Fee for multiple ticket purchases.
The system calculates as expected for one (1) ticket purchase (see Example A), but it is not calculated properly for multiple purchases. (see Example B and C)
Our multi-vendor event ticketing system runs on WordPress and uses Modern Events Calendar as the event post function, Dokan to allow for multiple transaction fees, and Stripe Connect for payment processing.
** How It Works **
Ticket buyers absorb all fees, and organizers receive the exact asking price per ticket sold after the payment processor deducts and splits the fees. If a ticket is $5, the vendor will net $5 after all fees are processed. (see Example D)
For example, one $5 ticket plus our Service Fee (3.5% plus $1.29 per ticket sold) plus Stripe’s Processing Fee (2.9% plus $0.30 per transaction) comes to $7.04. Once processed through Stripe, Stripe keeps $0.50 and sends us our Service Fee of $1.54, leaving the vendor $5 as expected.
** How It Should Work **
The problem we are currently facing is, when more than one event ticket is purchased, our system is not calculating the service fees and processing fee accordingly.
Each ticket purchased, whether it’s multiple tickets for the same event or multiple tickets for different events, should incur a Service Fee of 3.5% plus $1.29.
For example, if I buy two $5 tickets for an event (whether it’s the same event or two different events) it should total $13.78 at checkout:
Subtotal should = $10
Service Fee should = $3.08
Processing Fee should = $0.70
The expected result is to see the vendor receive $10 and the $3.78 fees split between us and Stripe accordingly.
// IDEAL SKILLS //
**Payment System Expertise:** Experience working with Stripe Connect and experience in fixing and fine-tuning payment systems is crucial.
**Event Ticketing Systems Knowledge:** Prior experience with event ticketing systems would be a big plus.
**Programming Skills:** Proficiency in necessary programming languages and software is a must.
// KEY DETAILS //
**Issue with Current Payment System:** The current payment solution is not calculating payments accurately. This issue needs to be resolved promptly.
// OBJECTIVE //
The objective of this project is to edit our code for our payment solution so it will calculate the correct Service Fee and Processing Fee for multiple ticket purchases.
The system calculates as expected for one (1) ticket purchase (see Example A), but it is not calculated properly for multiple purchases. (see Example B and C)
Our multi-vendor event ticketing system runs on WordPress and uses Modern Events Calendar as the event post function, Dokan to allow for multiple transaction fees, and Stripe Connect for payment processing.
** How It Works **
Ticket buyers absorb all fees, and organizers receive the exact asking price per ticket sold after the payment processor deducts and splits the fees. If a ticket is $5, the vendor will net $5 after all fees are processed. (see Example D)
For example, one $5 ticket plus our Service Fee (3.5% plus $1.29 per ticket sold) plus Stripe’s Processing Fee (2.9% plus $0.30 per transaction) comes to $7.04. Once processed through Stripe, Stripe keeps $0.50 and sends us our Service Fee of $1.54, leaving the vendor $5 as expected.
** How It Should Work **
The problem we are currently facing is, when more than one event ticket is purchased, our system is not calculating the service fees and processing fee accordingly.
Each ticket purchased, whether it’s multiple tickets for the same event or multiple tickets for different events, should incur a Service Fee of 3.5% plus $1.29.
For example, if I buy two $5 tickets for an event (whether it’s the same event or two different events) it should total $13.78 at checkout:
Subtotal should = $10
Service Fee should = $3.08
Processing Fee should = $0.70
The expected result is to see the vendor receive $10 and the $3.78 fees split between us and Stripe accordingly.
// IDEAL SKILLS //
**Payment System Expertise:** Experience working with Stripe Connect and experience in fixing and fine-tuning payment systems is crucial.
**Event Ticketing Systems Knowledge:** Prior experience with event ticketing systems would be a big plus.
**Programming Skills:** Proficiency in necessary programming languages and software is a must.