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

Method for /api/lookup/fees #16

Open
ecwyne opened this issue Jan 7, 2022 · 3 comments
Open

Method for /api/lookup/fees #16

ecwyne opened this issue Jan 7, 2022 · 3 comments

Comments

@ecwyne
Copy link

ecwyne commented Jan 7, 2022

In the docs: https://sandbox.fluidpay.com/docs/api/#fee-calculation

I'm ultimately looking to call this method (/api/lookup/fees) using a customer vault record rather than a bin and looked to this library to see how to format the API call only to find that it doesn't exist in this library.

Any assistance would be greatly appreciated.

@bvoelker
Copy link
Contributor

Thanks for reaching out. I completely understand your need for the fee calculation endpoint. I know we currently have docs for it but I would suggest not using that endpoint right now as we are actively making updates to that endpoint and fields are subject to change. I know that might now be ideal right now but we need to make sure we get the fee calculation perfect and dont want to rush it.

@bvoelker
Copy link
Contributor

Do you have a specific set of values you need to pass and exactly what you expect to get back that i can make sure is perfected in the next upcoming updates?

@ecwyne
Copy link
Author

ecwyne commented Jan 10, 2022

Thanks for the info @bvoelker. Being able to calculate fees from the server rather than the browser (via the tokenizer) is a mandatory requirement for my customer.

Given a customer vault record and amount to be charged, I'm looking to get back the surcharge amount for the transaction.

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

No branches or pull requests

2 participants