#monove - Server Driven Integration

1 messages · Page 1 of 1 (latest)

broken raven
#

Hi 👋

digital star
#

👋

broken raven
#

So you are trying to toggle between JS integration and Server Driven integration?

digital star
#

yes

#

we were actually trying somemthing a little bit more novel. theres a gap that we never had until now that we're trying to figure out how to fill.
until now we were aware of the payment status changes from onPaymentStatusChange

#

between collectPaymentMethod and processPayment

#

we would love for there to be a hybrid option where we can listen for the event locally - if available -

broken raven
#

I'm not sure I follow. Each integration path is an all-in situation.

digital star
#

ok so nmm that novel idea. back to my original question

broken raven
#

Yeah let me reach out to the team behind that integration path to see if it sets anything on the reader. When you say "clear cached credentials" what are you referring to explicitly?

digital star
fresh fable
#

👋 I'm hopping in since @broken raven has to head out soon - give me a minute to catch up

#

Out of curiosity - are you getting specific errors/what behavior are you seeing when you attempt to go back to using the javascript implementation?

digital star
#

connection status changes to connecting but connectReader fails. it has the correct ip in the reader object that comes back from discoverReaders

fresh fable
#

Interesting - and has this device worked with the JS Integration in the past?

digital star
#

yes

fresh fable
#

Can you share the reader serial number and also run through some quick steps for me?

  • ping the reader ID address from the POS
  • tell me output from running nslookup https://192-168-1-55.abc123.device.stripe-terminal-local-reader.net (replace the numbers with your IP address and replace abc123 as well)
digital star
#

can we switch issues here. weve got a terminal which we made go offline.

#

Reader ID
tmr_EujYeQcaEWcg9d
Serial number
WSC513142031615
Model
BBPOS WISEPOS_E
Last seen
1 minute ago

#

and we're getting back

#

{
"error": {
"message": "Reader is currently unreachable, please ensure the reader is powered on and connected to the internet before retrying your request.",
"type": "invalid_request_error"
}
}

#

the last seen is updating as we talk but we cant send it a paymentIntent to process

#

what can i do to help you debug this now?

# 
     "id" => "tmr_EujYeQcaEWcg9d",
     "object" => "terminal.reader",
     "action" => [
       "failure_code" => null,
       "failure_message" => null,
       "process_payment_intent" => [
         "payment_intent" => "pi_3LTVLmB26iHaRoZC0qHhndpO",
       ],
       "status" => "in_progress",
       "type" => "process_payment_intent",
     ],
     "device_sw_version" => "2.5.2.0",
     "device_type" => "bbpos_wisepos_e",
     "ip_address" => "10.0.0.240",
     "label" => "Monish's Terminal",
     "livemode" => false,
     "location" => "tml_DhBN5gNkzNSOeG",
     "metadata" => [],
     "serial_number" => "WSC513142031615",
     "status" => "online",
   ]```
#

example of failed request: req_NPqxgiy3LCMpTP

#

it finally allowed us to send it a payment intent after 10 minutes

true trail
#

Thanks for the info, karbi has to step out but I am catching up and will get back to you with what I can find soon

digital star
#

thank you

true trail
#

Apologies, took me a bit to get caught up on the whole server. So you are entirely interested in figuring out what happened with the Terminal that took 10 minutes to connect now?

#

Or maybe not connect, just get in to a state where you could send the payment intent?

digital star
#

i just want that when i see "last seen at" in the stripe dashboard, the terminal should be available to process a payment inntent

true trail
#

Gotcha. Apologies again for the delay, I am having trouble looking further in to this but will reach out to colleagues who should have a better idea.