#dcboy_api
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1349628416051118133
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hello
How to set parameters to reject cards that cannot be incrementally pre-authorized? How to re-initiate a payment for transactions using tap to pay?
Hi there,
You can use these test amounts to test your terminal integration https://docs.stripe.com/terminal/references/testing#physical-test-cards
Our business is in the field of unmanned self-service vending machine retail. We use tap to pay for a buy now, pay later approach, utilizing pre-authorization followed by deduction. Currently, we are facing a situation where a consumer was pre-authorized for $5, but the actual consumption was $10. The incremental pre-authorization failed, resulting in a loss of $5. Are there any ways to avoid this, apart from increasing the pre-authorization amount by $5? Is there any other method to determine if a credit card supports incremental pre-authorization?
Additionally, in another scenario, after settlement, we want to charge the consumer again. How can this be achieved?
Or you can authorize a higher amount and only capture the necessary amount?
If the authorized amount is too high, consumers will resist.
What technical means can be used to solve this problem?
There's no way to prevent insufficient_balance card decline. You'll want to communicate clearly to your customer that $x is the maximum amount that your service will charge, and you'll refund the appropriate amount later.
i have already config the CardPresentParameters must setRequestIncrementalAuthorizationSupport but Still unable to operate incremental pre-authorization
Did you encounter any error?
My understanding was that after setting this parameter, all the bank cards I receive would allow incremental pre-authorization operations, but in reality, that is not the case.
Do you have a paymentIntent that I can take a look at?
https://dashboard.stripe.com/logs/req_gC4JRtnj287i8j based on the request log, this card was declined due to transaction_not_allowed
The transaction_not_allowed decline code indicates that The card was declined for an unknown reason. The customer needs to contact their card issuer for more information.
Reference: https://docs.stripe.com/declines/codes
ok
Therefore, how can I safeguard the rights and interests of our merchants in this situation?
https://docs.stripe.com/payments/place-a-hold-on-a-payment-method you should put an authorization on card, and capture it later.
i have hold the payment method
but it will be expired
it's Manusl CaptureMethod
https://docs.stripe.com/terminal/features/extended-authorizations you can consider extending the authorization
You can contact support if you’re unsure about the eligibility of your merchant business category. If you’re a Connect user, set the merchant category code for your connected accounts to match their businesses.
Does our account support it?
We are in connect mode.
How can our sub-merchants confirm whether Extended authorizations are supported
You can reach out to support via https://support.stripe.com/contact