I'm testing onboarding for a a Standard Stripe Connect account, following the docs and using the phone number 00000000000 but:
I've tried 9 zeros and 10 zeros but both give the same result. I also tried removing the country prefix, but you have to select a country (removing country code is not an option).
Docs do say:
Force-skip the account form instead of having to fill out an entire account application (Standard)
But what if I want to see what customers see? Is that simply not possible, even in test mode?
That test phone number is specifically for Express onboarding, with Standard you'd skip the form entirely as you pointed out.
If you want to see what customers see, you could add a real phone number to get through the flow but stop short of actually submitting the form.
Related
Here is what I am looking to setup & I'm wondering if it is possible:
I have a classified ads site where people can join the site and then are allowed the ability to email any listing. I would like to add the ability for people to text message listings as well.
Listing owners would add their cell numbers if they would like to be contacted via text message, the site would then allow user to text BUT it would not show real phone numbers, each listing owner would be assigned a nexmo number and if they choose to give out their phone numbers, they can.
Then, I would also like the ability to send out a general broadcast to all users. Is this possible? And, if so, how would I integrate something like this?
Yep all of that is possible with Nexmo you seem to have 3 or 4 separate use cases here so lets break those down:
When your users sign up for your site you'll want to capture their Cell numbers against their account, you might want to use the Nexmo Verify product as part of that signup to ensure you have a correct and valid mobile number.
For users to be able to add listing via text you would need to get a nexmo number for them to send their listing to, that would be one number for the whole site and you could look at the senders number to link the message to an account (from the one you captured at registration) If you don't recognise the sender of a listing message then you'll want to send back some kind of response asking them to register and a link.
For buyers to contact sellers without revealing their numbers this is a very common use case called 'Message (or Call) Proxy' you need to rent a number for each seller (or listing) so you'll need to factor that into your pricing, then you forward any messages sent to the number to the seller, you will also have to implement some logic to handle replies and track state in your application, within SMS there is no concept of a reply so each message has no association with the previous one, this is a bit tricky when you have several conversations going on over the same number.
Finally the 'broadcast' this would just be a case of iterating over the list of numbers you have for your users and sending the message to each one, you will need to ensure that you comply with any regulations around sending of bulk messages in the country you are sending to, more details for that are on the nexmo knowledgebase https://help.nexmo.com/hc/en-us
I'm attempting to create a google nest client to write electricity monitor data to the Nest for display in the energy history plot, but although I'm able to create a test client with thermostat read permissions, when I attempt to create a new client with product data write permissions I get an error message saying "scopes.justification exceeds required maximum length of 140". I don't see any fields with more than 140 characters and an email to the Nest team has been unanswered for several days.
I should say I'm leaving the OAuth redirect field blank because I'm still trying to learn exactly how OAuth is meant to work and if the redirect is a site I need to write and host or what, but it appears to be optional and one can edit client details later or use a PIN so doesn't seem that's the issue, but I could be wrong.
Anyone had this issue or able to provide some tips?
I am trying to send SMS to the people all over the world using a non-registered short codes, but the sms cannot be delivered to US or Canada. How do I achieve this?
Is there an API to get information of the country using a phone number, so that I can know if the current number is of US or Canada's?
(Disclaimer: I work at Nexmo.)
To identify US vs CA numbers you can use Nexmo's Number Insight API. Besides the country you can also get lots of info, landline or mobile, carrier, reachable or not, etc.
If you you want to send to the US using short codes without needing a short code yourself, you can also use our US Short Codes API. If your use case fits into what we support (two-factor authentication, alerts, or marketing).
adsense management api give me different results than the website interface.
the simplest example:
run the report here:
https://developers.google.com/adsense/management/v1.4/reference/accounts/reports/generate
I want to see the rpm by countries for given AD_UNIT_NAME for some date
this the request:(xxxx is censored
https://www.googleapis.com/adsense/v1.4/accounts/pub-xxxx/reports?startDate=2014-05-01&endDate=2014-05-01&dimension=COUNTRY_CODE&filter=AD_UNIT_NAME%3D%3D160%2F600+-+xxxx&metric=AD_REQUESTS_RPM&key=xxxx
I get the results as excepted the problem is when i go the adsense website and click on the same ad unit name, and add country dimension I see different results.. i checked it a lot of times with all kind of differents request(for example clicks instead of rpm or different ad unit or without country dimensions and so on).
the api always give different results than adsense interface why is that?
api results example:
[
"BR",
"5.10"
]
adsense website results for same ad:
brazil: 7.64
what i tried:
make sure same currency.
make sure same dates.
check different dates.
check its the same ad.
check different ads.
etc.
so after long time I found the answer:
different time zone...
all was needed was to set useTimezoneReporting to true.
I think it should be the default value..
Anyone else have this problem?
I cannot sign up for an Azure account.
On the registration page, it asks for your phone number and wants to confirm it by sending a text or calling you. I only have a Google Voice number, and I always get
We were unable to verify your account
No matter if I choose text or call. There is no way around it. Any help?
EDIT: Other posts have indicated it's a problem when your country isn't listed, but that is not the case here (I'm in the U.S.). Those posts suggest calling "your local Microsoft branch" but how do I find that?
.
After reading the comments above, and calling Microsoft myself, I was told the verification process does not support Google Voice or Skype phone numbers.
The person I spoke with on the pre-sales department of Azure said he could not manually create an account for me or validate my Google Voice number, despite me sending him this question on StackOverflow showing that others had been successful in calling Microsoft as I had.
My solution was to use a friend's number and have him send me the verification code he received. However, it must be within the Azure signup's session timeout period or the code is no good.
I really hope someone at Microsoft sees this and corrects it for future customers.
I wanted to throw in a answer for Republic Wireless users who are having this problem.
I know this doesn't pertain specifically to Republic Wireless, but this is for those users, and should perhaps prove helpful, since this is the 1st result from Google on the error message.
Republic Wireless is a VoIP company, but they still use an underlying sprint phone number to handle calls/texts when you are not under WiFi, here is how to access your underlying phone number so you can get past the Windows Azure registration verification:
Open the Phone app (the standard dialer that comes with the phone).
Dial ##786#.
The number shown for Mobile Number is your Sprint number.
Hit the Back or Home button to dismiss the information screen.
https://community.republicwireless.com/people/carlh/blog/2013/11/20/moto-x-how-to-find-out-your-phones-sprint-number
I faced this exact same error. After trying different solutions, i decided to change my browser from Google Chrome to Microsoft Edge - and i was able to verify my account thereafter