#mauliks_code

1 messages · Page 1 of 1 (latest)

main gazelleBOT
#

👋 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/1433077361699590146

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

void patrol
#

hey there, can you please explain more about what you're trying to test and how this error arises?

warm eagle
#

I am just trying to accept money and using terminal simulator for iOS

#

let me know what else info I can provide ?

void patrol
#

Are you specifically trying to test PIN entry, or is this coming up unexpectedly for you?

warm eagle
#

unexpectedly only

void patrol
#

Your logs say

collectPaymentMethod succeeded
So are you getting a payment method then? Can you share an example payment intent?

warm eagle
#

how to get payment intent ? from the app log?

void patrol
#

Or your server, wherever you're creating the intent you use with terminal

warm eagle
#

fetchConnectionToken you mean?

#

{
object = "terminal.connection_token";
secret = "pst_test_YWNjdF8xT2xRM0NIWGxmaWF5cWFaLGV3MUpYbjRBRHVuMkNZb3l6Z3NxdWdLa2EwcXllZkg_00jGd6fewL";
}

#

is there anything changed?

void patrol
#

It sounds like you're trying to discover/connect to an actual reader via bluetooth, not the simulator

warm eagle
#

yes I got it and now showing simulator list of readers

void patrol
#

Ok and then you can connect to one of those

warm eagle
#

yes

#

now trying to get intent of transaction

#

<SCPPaymentIntentParameters: 0x600003059560; amount = 175; currency = usd; metadata = (null); onBehalfOf = (null); stripeDescription = CIA - Payment by Aimee Radford & ID - 18713; statementDescriptor = (null); statementDescriptorSuffix = (null); receiptEmail = (null); applicationFeeAmount = (null); transferGroup = (null); transferDataDestination = (null); setupFutureUsage = (null); captureMethod = automatic>

#

is this what you mean by intent?

void patrol
#

Either a setup intent or payment intent id: seti_1234 or pi_1234 etc

warm eagle
#

<SCPConfirmPaymentIntentError: 0x6000018b4440; code = 6000; message = Allowable number of PIN tries exceeded. In testmode, using a physical test card with designated amount ending values produce specific decline responses. See https://stripe.com/docs/terminal/references/testing#physical-test-cards for details.; requestId = req_76rA6m4k2D6BiJ; requestError = 0x600000d91e30; paymentIntent = pi_3SNZbhHXlfiayqaZ16oPDLyL: 0x600003b148c0>

void patrol
#

As linked in the error

#

75 Payment is declined with an pin_try_exceeded code.

#

You used:

amount = 175

#

This error is expected because of the amount you're using

#

If you are not specifically trying to test this error, you need to use a different amount, like amount = 200

warm eagle
#

amount = 175 is the issue here?

void patrol
#

Any amount ending in 75 will trigger this error

#

yes

warm eagle
#

lol

#

my cart has 150 + 25 2 items

#

let me try with other amount

void patrol
#

Yep, use different items/amounts

warm eagle
#

done ! 😄

void patrol
#

As the doc linked in the error shows, several different amount ending values trigger specific errors

warm eagle
#

this was unexpected thing

void patrol
#

If you're just trying to test happy path flows without errors, i suggest using all amount as round whole dollars, eg 100, 1000, 4200 etc

warm eagle
#

understood

void patrol
#

that way no matter what comibnation of items you pick will also be whole dollars and not trigger these errors unexpectedly

warm eagle
#

thanks a lot !

void patrol
#

NP!

warm eagle
#

humans are always ahead of AI !