AnsweredAssumed Answered

Processing Fees through the API

Question asked by mgreineder@masonicvillages.org on Mar 29, 2017
Latest reply on May 8, 2017 by gjsissons

Like • Show 0 Likes0
Comment • 2

I am trying to build an integration using straight APIs that would allow a customer to make a payment via eCheck or Credit Card. The issue I am having is I want to allow the user to pay the transaction fee only using the APIs and not the hosted page. Can I do that using a flag or indicator in the API and how would I retrieve the amount? It seems like if I manually calculate the x.x% and add it to the total, then x.x% will come off of the new total and charge more. For example if I want to charge $100 and my fee is 3%, I could end up sending in $103 for the total transaction amount but then 3% would be charged to $103 and end up with a final amount deposited to the bank account of just under $100

No one else has this question

Outcomes

Chris Jennings Mar 31, 2017 2:50 PM

Hi Michael,

Great question...but it has thrown some of us for a loop. I am working to track down the right person to answer your question and we will get back to you soon.

Regards,

Chris

Actions

gjsissons May 8, 2017 9:39 AM

Hi Michael,

Just so I understand the scenario, I gather you are trying to expose a payment amount via a hosted page for an amount like $100.00, and then programmatically submit a transaction outside of the hosted payment context for some additional amount.

I'm just wondering what the exact scenario is - are you seeking to gather the extra 3% as a service fee on top of the transaction amount (to pay a commission for example) or are you trying to add a percentage to buffer your merchant from processing / credit card fees? Would the 3% be part of the original transaction or as a separate transaction?

I ran into similar scenarios previously when attaching "convenience fees" to purchases. I also dealt with another scenario where I wanted to carve out a chunk of every payment and send it to do a different account. (in my case I was accepting a payment but wanted to keep 1% myself as a registration fee for using my service and send 99% to the merchant behind the scenes)

They may be off base, but I'm wondering if it might be practical to do some client-side JavaScript manipulation to expose a fields where a visitor enters the payment amount in a field under your control and then use a JavaScript "onchange()" trigger to run a JavaScript function that calculates the actual amount to authorize and populate a hidden field? I'm thinking this approach would give you more flexibility in handling the transaction. Very possible I'm misunderstanding the requirement though.

Actions

2 Replies

Chris Jennings Mar 31, 2017 2:50 PM
Mark Correct
Correct Answer
Hi Michael,

Great question...but it has thrown some of us for a loop. I am working to track down the right person to answer your question and we will get back to you soon.

Regards,
Chris
Like • Show 0 Likes0
Actions
gjsissons May 8, 2017 9:39 AM
Mark Correct
Correct Answer
Hi Michael,

Just so I understand the scenario, I gather you are trying to expose a payment amount via a hosted page for an amount like $100.00, and then programmatically submit a transaction outside of the hosted payment context for some additional amount.

I'm just wondering what the exact scenario is - are you seeking to gather the extra 3% as a service fee on top of the transaction amount (to pay a commission for example) or are you trying to add a percentage to buffer your merchant from processing / credit card fees? Would the 3% be part of the original transaction or as a separate transaction?

I ran into similar scenarios previously when attaching "convenience fees" to purchases. I also dealt with another scenario where I wanted to carve out a chunk of every payment and send it to do a different account. (in my case I was accepting a payment but wanted to keep 1% myself as a registration fee for using my service and send 99% to the merchant behind the scenes)

They may be off base, but I'm wondering if it might be practical to do some client-side JavaScript manipulation to expose a fields where a visitor enters the payment amount in a field under your control and then use a JavaScript "onchange()" trigger to run a JavaScript function that calculates the actual amount to authorize and populate a hidden field? I'm thinking this approach would give you more flexibility in handling the transaction. Very possible I'm misunderstanding the requirement though.
Like • Show 0 Likes0
Actions

Processing Fees through the API

Outcomes

Related Content

Recommended Content