i have searched a lot but only got following login url for sagepay test account.
https://test.sagepay.com/mysagepay/login.msp
Can any one please help me from where i can create account to log in at above screen.
I have already created simulator account at
simulator account
To use this test sagepay login you need a normal sagepay payment gateway / merchant account or have a MySagePay account. This test URL is given to clients who have access to the live side for their day to day transactions.
If you have an account with Sage you can get them to set up the test environment for you.
create mysagepay test account
http://www.sagepay.co.uk/sign-up-for-beta-testing
Related
I'm quite new to laravel and payment integration.
I want to give an option to my web panel users to connect their paypal account with their own personal account on my web panel to receive payments.
and I want to give them a connect button for them to proceed.
Can someone please help me achieve the same.
Thanks in advance
You can use Log in With PayPal, possibly with the Partner Referrals API, to have them log in and get their PayPal account ID. This can be set as a payee.
Alternatively, you can ask them for their Client ID and/or Secret for a live REST APP, which they can log in there to obtain.
Google play console is requesting to verify my identity.
The problem is that the verification form is asking for an organization info and docs while the account is for individual and that is provided in the account details screen.
So what am I missing? Where to go? Or how to contact google support?
I had this after emailing googleplay-developer-support#google.com. Solution: Your payment profile shouldn't be set as organization if your developer profile is set to individual and vice-versa.
Per checking, the payments profile associated with your account is set as an organization. You may choose to verify your account as an organization with the following documents that our system accepts: Certificate of Organization, and a valid ID of the organization's Official Representative.
If you would like to verify as an individual and change the entity type on your payments profile, you would have to create a new account in order to change from organization to individual. You may view your payments profile via pay.google.com
To change the entity type on your Payment Profile, it would need to be deleted and created again. Since a Play Console account can only be associated with one Payment Profile, it will need to be deleted and recreated as well.
To resolve the issue, we can close your Play Console account and refund the registration fee. Then, you can delete your payment profile at pay.google.com before you sign-up for a new Play Developer account. To proceed, please provide confirmation by responding with “I confirm to have my Play Console Developer account closed and have its registration fee refunded.” Also, please remove the existing draft app from the Developer account
I had this issue recently and it turned out it was because I had an old Payment Profile with Account Type of 'Organisation'.
You need to go here: https://pay.google.com/gp/w/u/0/home/settings
Personally, I had two payment profiles; one was for an Individual and one was for an Organisation. Maybe the Organisation one was the default or whatever.
In the end I managed to close that payment profile and create a new developer account after having the first one refunded.
There were a few emails to Google Support going back and forth but that solved it in the end and now I have an app on the Play Store.
Trying to setup an app with a sandbox account on PayPal. I already had a Business account with PayPal and have created a new application under the Sandbox.
I am provided with 3 credentials by PayPal:
Sandbox account which has the appearance of an email address
Client ID
Secret
However, using Omnipay with Laravel and it asks me for Username, Password and Signature in the config/env. I have some legacy prod credentials which look nothing like those provided by PayPal above, so can't even make an educated guess.
Thank you in advance.
Client ID/Secret are API credentials from a REST App (which if for sandbox mode will be tied to a particular sandbox account when the app is created)
For the old classic NVP/SOAP API Username/Password/Signature credentials, go directly to the sandbox account list and in manage accounts (...) select View/Edit account, second tab.
I am just getting started with the google classroom api. I signed up for the developer test accounts and have 1 teacher account and 2 student accounts. I created a couple of classes and enrolled the 2 students in the classes. I want to use the api either via .NEt or Javascript. The prerequisuites state that I need a Google Apps for EDU account with Google Classroom enabled. How do I get this? Also, I assume without having the Google Apps for EDU account I cannot perform the first step:
"a) Use this wizard to create or select a project in the Google Developers Console and automatically turn on the API. Click Continue, then Go to credentials."
When I perform this step when logged in under the teacher account I get an error:
Error
"Developers Console has not been activated for your account. Your account may be suspended or disabled. If you are a Google Apps user, ask your domain administrator to enable Apphosting Admin on your account."
To obtain a Google Apps for Education account, you have to register your domain (or buy one), and fill up this form.
When filling the form, you will get information about the requirements needed to get the account.
To create a project in the Developer Console, you can do it even from your gmail account. After you created the project, you can enable the Classroom API so you application can access it.
When you run the code, you will have to login with a valid account (teacher or student). If you try to access the API with an invalid account you will get an error.
You can also use the Classroom API methods in the documentation. For example the resource curses.list has a "try it" section, where you can try the API before creating any project. There you can see how it works.
To be able test any implementation of Android Market licensing (e.g. LVL, In-app Billing), Google advises to create a Google Checkout test account, since the developer cannot buy from himself using his own Google Checkout account.
Sounds great except that the test account must use a real credit card.
Which begs the question: How is this different from a normal account? What is the advantage of a test account over a normal account?
The test account does not have to be associated with the google checkout account. The publisher can have his/her google checkout account set up against the android market account. And as a developer, you can have a test account created.
Test account holders can test the application for LVL and in-app purchasing, etc only if the application is uploaded on the developer console. It does not have to published. But it has to uploaded and activated and saved.
So, it's not true that the test account holder has to have his/her financial details registered with the Google servers. Only the publisher has to do that. And the publisher can add as many test account holders as he/she desires. The publisher will provide a publishing key and that's all the developers need to implement/test their code.
Look for documentation on Google developer site. It explains well.
HTH.
You don't need a separate test account. That's only if you want to include others as testers. Your own publisher account is just fine. If you set the LVL response in your developer account to, say "UNLICENSED" for testing purposes, then only the devices that are set up with that Google account will get this test response.