We have developed an application to send notification through WhatsApp using MessageBird integration.
In Facebook - WhatsApp Management painel our account is in "Sandbox mode" which means that we can only send up to 10 messages/day to only 2 numbers. Detail: our company is already verified and the account status is approved.
Is there anything we are missing? Any help?
There are two prerequisites for your phone number to be promoted from the "sandbox mode":
Your business needs to be verified on Facebook (as shown in this video)
Your WhatsApp Business Account needs to be approved. You can easily check this by navigating to this page and finding the account under "Accounts > WhatsApp accounts". After finding the relevant account in that list, select "Settings". Your account status should show up as "verified".
In case you need help verifying your business and/or approving your WhatsApp Business Account, please reach out to MessageBird support. If both of these are in order and your phone number is still in sandboxed mode, this is also something they should be able to help you with.
Related
I have successfully setup my account on whatsapp developer app by meta and can send messages to 5 free users. Now the question is how can I go live with the app. I have no verified business manager account, is that necessary?
What will I need to do after verification of business account? Do I need to generate permanent access token and it would work fine?
Plus I need to know how can I send messages to groups on whatsapp?
Yes, you need to become a verified business account and all would work as you saw with the demo account, with no restriction on the number of destinations.
First 1000 conversations/month it's free, you can check details here: https://developers.facebook.com/docs/whatsapp/pricing/
Bear in mind, you will NOT be able to message groups with the WA Cloud API. If you need to, you will need to rely on custom APIs that do that. There are some available, see the one shown here:
https://youtu.be/lCmoay0G86M
We faced with testing problem on the side Google Pay.
At the current stage, we get into the GPay only after Card registration on the side of our site, when after filling out the form user is redirected to the GPay page to create a new Card.
A Card is being created : we see it with the data that is entered into the form, but the GPay doesn't send any requests to our site. A special test environment from GPay is needed?
Google Pay's support service asks: "Are you receiving the POST from GPay when you attempt the enrollment flow from the app?"
How we can apply from GPay if we can't create a Card from GP at this stage?
The process of creating a Card is described in paragraph 1 (on the site side).
How to get into the GPay for enrollment at the testing stage?
Support service writes "When you submit your user details from GPay, it sends a POST request to your server so that when your page is displayed it contains the information from the user data form. "
As we pointed, at the current stage we can't send data from the GPay.
It was expected thatGoogle Pay's support service send a POST request to our site, but we don't see POST request's body. It is empty.
Therefore, we asked earlier, What internet service we can see it with?
They answered, as we understood, that we can see it by sending from GPay.
How to send it from the GPay, if at the testing stage we can only see
newly created cards and we don’t get any requests from GPay?
Is testing take place from GPay app?
If so, why don't we have an access?
We get a request POST, but with an empty request body.
The GPay has a lot of users with the Loyalty Card.
Someone has already come across this.
We didn't find such situations on the Internet.
How anybody have handled situations like this before?
How to create a new Card from GPay and see a POST request?
We do not have access to the class settings in the account. On Russian language, we do not see the callback feature, and on English technical support sends to us a screenshot - there are settings in the account. Could there be access rights issues?
To accoding with your link from paragraph 5 https://developers.google.com/pay/passes/rest/v1/loyaltyclass#discoverableprogrammerchantsignupinfo - we did not find the insert barcode /manually settings. Can you tell us where to find them?
At the moment, we can scan the barcode in GPay app(due to help of GPay support service ), but we do not receive a Post request after inserting bar code in GPay app.
Our Russian account settings looks like:
GPay support service see our account on English so:
We don't see these settings for barcode.
In accordance with the documentation https://developers.google.com/pay/passes/guides/overview/how-to/use-callbacks, we set up a callback feature, but we do not receive a post request in the format json (php):
$responseJson_str = file_get_contents('php://input');
$responseJson = '[' . $responseJson_str . ']';
$response = json_decode($responseJson, true);
var_dump( $response);
$file_server = "server_calback.log";
$fw = fopen($file_server, "a");
fwrite($fw, "POST " . var_export($response, true) . "\n");
fclose($fw);
What is wrong?
I show a screenshot with the request POST to our site
https://itcrk.icu/testcallback.php
from https://reqbin.com/
At the beginning of testing stage, we implemented signin / signup as you indicated in points 1-6. We did this functionality was not because we needed it, but thought that it was necessary for testing.
Then we wrote in support team that we need a barcode/manually, as users of other cards are used to. We were answered that we need settings in the account, we did not find them. Support team helped us to configure the barcode in the account of the Merchant Center - Google.We insert barcode in the GPay , but we don’t get json on the site. We assume a problem with access rights in the Merchant Center - Google. How do other cardholders usually set up a barcode in their accounts? We do not have access to the settings n the Merchant Center - Google, unfortunately. Support team writes that there should be access, but it does not.
It turned out that there are two ways to work with cards in the GPay. The first method is described in the documentation here https://developers.google.com/pay/passes/guides/enrollment-signin, the second method is to scan the card(barcode/manually) and use it as a card storage, but card data is not sent to the user’s server.
The Loyalty card is simply displayed in the GPay with its number(from barcode/manually) and that's all.
Sign up and enrollment are triggered from the google pay app: https://developers.google.com/pay/passes/guides/enrollment-signin
You will see post once a user goes into the Google Pay app and hits add pass then finds your program and hits sign up/ sign in.
See 1-2.
You have to use the account you provide to support team - its only visible for them for testing.
It may not be from Google. Google requests have the body with the user details.
Go to google pay app and sign in with user that is whitelisted by support to see the program. Hit add pass, then loyalty program then search for your program then hit sign up/ sign in and it will post to the endpoint defined here: https://developers.google.com/pay/passes/rest/v1/loyaltyclass#discoverableprogrammerchantsignupinfo
Let me also clarify enrollment and sign in. This is what a user sees, what the Google Pay app does and finally what a merchant needs to do:
Google Pay user navigates to passes tab in Google Pay App, hits "+ Pass":
Google Pay chooses which type of pass to add, hits loyalty for this example:
User searches and presses on the specific program they want to sign up for (theres a testing phase before it goes public, in which only accounts which you tell support team can see the program in google pay app):
User then fills out information to share and consents to share their information with this merchant, then they press continue.
Google Pay Then does a POST request with user info to endpoint defined here on the loyalty class by merchant: https://developers.google.com/pay/passes/rest/v1/loyaltyclass#discoverableprogrammerchantsignupinfo
Here is where merchant, yourself would have to be listening for POST to endpoint you defined in the setting mentioned previously and give user form to finish providing all details needed and then redirect to the JWT link to automatically save the pass.
See https://developers.google.com/pay/passes/partners/enrollment-signin for reference.
It turned out that there are two ways to work with cards in the GPay. The first method is described in the documentation here https://developers.google.com/pay/passes/guides/enrollment-signin, the second method is to scan the card(barcode/manually) and use it as a card storage, but card data is not sent to the user’s server. The Loyalty card is simply displayed in the GPay with its number(from barcode/manually) and that's all.
Not able to create PAYFORT Sandbox test account.Where I get merchant identifier number.
How to register PAYFORT test account
How to get the merchant_identifier
How to get the access_code
How to get the service_command
I do not have any Idea about PayPort.Please share any Example program related to Swift.From PAYFORT where I create the sandbox test account
"https://www.payfort.com/get-started/".From this link, I entered the personal details once complete the details try to login to PAYFORT, not able to log in.
I've been facing similar questions and so emailed the PayFort support team. Here is the response I got:
Good afternoon and thank you for contacting PayFort.
Please be advised that in order for you to have the account created
in the SANDBOX (https://testfort.payfort.com) environment, the first
contact has to be initiated by one of our Pre-Qualifications team
members after receiving a documented request in a form of registration
from our website. (www.payfort.com)
The pre-qualification stage entails knowing the company/
organization's business and requirements. Qualifications are as
follows:
The company has a legal setup in the countries mentioned on our
website. The company's business module is supported by PayFort.
For more information about the businesses we support and countries,
please click on this link: http://www.payfort.com/payfort-faqs/
After the qualification stage, one of our Sales Representative will
get in touch with you to get a deeper view of the business so as to
suggest the payment solution that would suit your requirements.
Then only the TEST/SANDBOX account is created by our team to start the
Integration process.
If you wish to proceed, please kindly register on the above link or
send a direct email to sales-uae#payfort.com.
Register your self on https://www.payfort.com/get-started/ by giving your company info and wait for the email from PayFort. they'll send you the info about your test account.
you can login your test account on https://testfort.payfort.com and find your access code and merchant identifier from "Integeration Settings" menu and "Security Settings" option. you can also see the attached image so you can easily find the access code and merchant identifier.
the service_command is a static value "PURCHASE" in capital letters.
Slovakia has been added recently to list of supported Merchant countries for Google Play.
I have an account in Czech Republic (CZK) paired with Merchant Account with active paid and free apps and want to change the country to Slovakia (EUR) - mostly because i of the fees related to money transfers from a different currency (CZK to EUR) on my business account.
I have been searching on Google but found nothing except for transferring all my apps to new developer account. I'm afraid that this will hurt my play store search positions and i won't be able to transfer the Google Play Services data (LeaderBoards, Achievements)
Also i want to keep the package names.
Had someone done this? How should i proceed?
June 2017 update:
Apps with subscriptions can now be transferred!!!
The original answer:
This is a complete answer I got from Google:
Hi,
Thanks for contacting Google Play Developer Support.
I understand you'd like to change the country associated with your Google Payments Merchant account. Once your Google Payments Merchant account has been created, it's not possible to change the country associated with that account. Instead, I can cancel and refund your existing developer account and transfer your apps to a new developer account that has the appropriate merchant country details.
To get started with this process:
Edit your current developer account name. If you'd like to continue to use your developer name with the new account, you’ll need to change your current name in order to free it up for the new account. For example, name the old account “xxx-OLD,” so you can use "xxx" in your new account. Make sure you save your settings.
Create a second Google Account (with a new, different email address). After you've created the new account, you will need to configure Google Payments with a billing address corresponding to your preferred merchant country.
After you've registered the newly created Google Play Developer Console account, create a new Google Payments Merchant account from the Developer Console. Pay special attention to the country listed for your legal business address. You may need to adjust your Google Payments settings if you haven't configured your billing address properly.
Use this online checklist to submit your app transfer request.
Please note however at this time, an app transfer can't be completed with in-app subscriptions currently or previously configured for your app; this includes subscriptions that do not have subscribers, or those apps which have had all subscriptions canceled.
I understand this limitation can be frustrating, and I apologize that we don't currently have a more seamless way to transfer these applications across accounts. We're actively working with our teams to design a better experience for developers with apps using in-app subscriptions, though we do not currently have an ETA.
I appreciate your understanding, and your dedicated support of Google Play.
Regards,
xxxxx
Google Play Developer Support
The country associated with your Google Play Developer account can't be changed. However, you can create a new account that uses a different country and transfer your apps to your new account.
To transfer apps to a new account, you'll need to prepare some account information. To learn what information you need and to send your request, go to the Google's app transfer checklist.
Reference: https://support.google.com/googleplay/android-developer/answer/139626
Using developer account of paypal I could get client ID and secret key by creating an app but not with the live account.
I am using REST API for transactions on my website where I ask users(who has paypal accounts) to enter their client ID and secret key, and use this info to transfer the money into their account, payments are done by credit card.
It is working fine with the developer account but where is the option to get client ID and secret key from live account ?
OR
Is there any other way I can do this, I want to transfer the money to paypal accounts and payments are always done from credit card.
This has changed at PayPal. (Quite a lot actually!)
As before - log in to your PayPal account at: https://developer.paypal.com
PayPal, like everyone else, Wants to show ads. So you may have to look around to actually get to the developer website. Just keep looking until you get to where it has "Log in" at the top.
Once logged in click on the "Dashboard".
Once to the Dashboard click on the "My Account" FIRST- BEFORE anything else.
Once to the "My Account" part make sure you can do everything (ie: there are GREEN check marks in both columns. Or if you don't want to do some things - make sure they are NOT check marked.)
To activate (or Enable) something just click on the link and follow what it says to do.
Once through with that click on the "My Apps" link on the left. If you are no longer where you can do that then go back to #2 above and start over.
Once on the "My Apps" page; click on the link to "Create App".
This will ask you to name the app and select an account to develop the app with.
Once through putting in all of that information - you are through and PayPal will give you all of the information you need.
I don't know about anyone else - but that's just a few more steps than just logging in and clicking a button. :-)
You should use the new Developer Portal to create your Apps and get sandbox and live credentials for each: https://developer.paypal.com/
Log in to https://developer.paypal.com and click the Applications tab.
On the https://developer.paypal.com/webapps/developer/applications/myapps click Create App.
On the Create New App page, provide an app name.
Click Create App, and then review the information displayed about your app (as described below)
now you will get client id and secret key