Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Holds pricing to tables #23

Closed
jeregrine opened this issue Jan 28, 2013 · 3 comments · Fixed by #215
Closed

Add Holds pricing to tables #23

jeregrine opened this issue Jan 28, 2013 · 3 comments · Fixed by #215

Comments

@jeregrine
Copy link

https://balancedpayments.com/docs/overview?language=bash#pricing

Does not cover the pricing of holds as .30C.

@mjallday
Copy link
Contributor

mjallday commented Feb 8, 2013

@jeregrine - Holds are implicitly included in the debits pricing "Balanced Processing costs just 2.9% and 30¢ per successful charge."

Does that make sense to you or are you saying it should be included in a separate section?

@jeregrine
Copy link
Author

It makes sense now that I understand it. Prior to the discussion here and
on chat I did not. It seems like something an outside needs to be
explained.

On Feb 8, 2013, at 5:56 PM, Marshall Jones [email protected] wrote:

@jeregrine https://github.com/jeregrine - Holds are implicitly included
in the debits pricing "Balanced Processing costs just 2.9% and 30¢ per
successful charge."

Does that make sense to you or are you saying it should be included in a
separate section?


Reply to this email directly or view it on
GitHubhttps://github.com//issues/23#issuecomment-13321505..

@remear
Copy link
Contributor

remear commented Aug 1, 2013

This should also be more clear in the new pricing page, balanced/www.balancedpayments.com#14

@ghost ghost assigned remear Aug 1, 2013
@remear remear closed this as completed Aug 1, 2013
@matin matin unassigned remear Apr 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants