-
Notifications
You must be signed in to change notification settings - Fork 46
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
tipUnits
in metaData does not contain tipUnits
#228
Comments
@yogen-p thanks for the report. We're tracking this issue with our internal issue tracker and it will be addressed in a future release. |
We've added this functionality with version 2.15.0. You can now see the tip amount through the PaymentIntent object in the processPayment callback. |
Hi @sjl-stripe This still seems to be broken on the latest SDK |
@yogen-p -- can you clarify the problem you are seeing? The Setting the on-reader tip amount in the metadata will not work because we only send the metadata to stripe.com when creating the payment intent. We are looking into supporting an |
Hi @billfinn-stripe , Thanks for clarifying that. The I was looking in the wrong place. Apologies for the trouble |
Summary
The tipping value is not in the response of the
processPaymentCallback
for WisePad3. So, I need to store the original transactionAmount and then substract it frompaymentIntent.amount
.Code to reproduce
Reproducible every time I make a payment with tip
Terminal.getInstance().processPayment(paymentIntent, processPaymentCallback)
Android version
12
Impacted devices (Android devices or readers)
Doesn't matter
SDK version
2.8.1
Other information
This transaction had a transactionAmount of £10.00(1000 units) and a tip of £2.00(200 units)
The text was updated successfully, but these errors were encountered: