I need to integrate the Master Card API to my application to request payment and send the money to a bank account!
The app is created in Laravel, developer.mastercard has many apis, reading on the page I see that it has many apis and the one that seems to adapt to my needs is moneysend.
Add the dependency as the document says
Composer requires mastercard/moneysend
But I'm confused how to continue!
Thank you very much
Install composer if you already haven't and then on terminal (while in your app folder), just type composer require mastercard/moneysend
This will execute the require command and download/import the dependency in your Laravel application
Related
I am trying to add the features of tracking the product that was bought from my site . I want to give the user detail about their product delivery and location of it like done by aftership. How can i implement it in my web site? How can i initiate it?
Please follow following step for aftership tracking integration.
Login to your AfterShip account.
Visit SETTINGS > API
Give your api-key a name and click Generate
integrate PHP sdk for aftership Aftership SDK
You can install SDK by composer require aftership/aftership-php-sdk command.
Please follow git document instruction.
We migrating our app from the old Marketplace to the new one. And we faced with the problem like described here - Google Apps Marketplace app installation callback
But we have special app architecture, it allows to the same user authorize multiple domains. For example we have user(authorized with google +) admin#tester1.com and he needs to install app for following domains:
tester1.com where admin account is admin#tester1.com
tester2.com where admin account is admin#tester2.com
For tester1.com we can use licensing API and check if app is installed and who installed it. We already have authorized account admin#tester1.com and the same user installed app.
No issues for this scenario.
Next user needs to install app for tester2.com. In process of installation(at the marketplace side) user switching to new account admin#tester2.com and installing app.
When user backs to us, we using licensing API again and check if app is installed and who installed it. At this step app will be installed, but it will be installed by user admin#tester2.com which is currently not connected to our app.
For this scenario, how we can securely recognize that domain tester2.com should be linked to user admin#tester1.com? Any recommendations/advices?
Currently we see only one way - require user to authorize admin account for each domain that he wants to install with our app.
This appears to be a special case, and Google don't have any guidelines around how to handle it. Deciding how to charge for and provision your application is left up to the developer.
We've migrated our app from the old marketplace to the new one. After a few days we've received an email that we don't comply with an SSO policy - the user is not recognized after he installs the application.
In the old app we had a specific setup link, that was opened for the user after he installed the app - thus making him recognizable. Is there such a function in the market? Is there some sort of a callback for the installation event in the new marketplace?
P.S. the guy from Google told me to post technical questions on Stackoverflow and that "Our developer relations team monitors that forum and will be able to assist you."
EDIT:
There's the Additional app setup link in this after-installation popup (which clearly no user will click):
Is there a way to call the URL that of the Additional app setup in the background, without needing the user to click an obscure link?
That was an intentional design change which is different than how it used to work in v1 of the marketplace.
If you need interactive setup, best thing to do is put in a check on login to see if the domain has been configured. You can use the licensing API to check for a marketplace install record or directory API to check user permissions if those matter for your use case.
If you just need to run a background task, you can periodically poll the licensing API to detect new installations of the app. This shouldn't be done too often, so if you need to do things before a user logs you're still better off going with a check on login to route them to the setup flow as needed.
I have setup my Django rest framework and started with my initial tutorial..Its running fine , but
I get this msg when I run it--
{
"detail": "Authentication credentials were not provided."
}
I have one user being setup ..Not sure I dont see in the resultset. When I go to shell and try User.objects.all(), I see that user.
I apologise if your problem is not be this simple, but have you authenticated with your Django site?
A quick way to get moving; go to the Django admin console, log in and then go to your API.
In older versions of Django you will have to enable the admin console in [project]/settings.py and [project]/urls.py.
https://docs.djangoproject.com/en/1.6/ref/contrib/admin/
I tend to have both open in separate tabs when I am building, and when I first started with rest_framework I didn't even realise that the tutorial leverages the django auth by default until I got to the auth part of the tute. I felt a bit silly being so complacent with how well some of this current gen tech works these days!
My team and I(the business/idea guy) are developing a new Startup using the Laravel framework. I'm not a tech guy but I want to learn as much as possible.
We began with installing and utilizing the Sentry Bundle, and then added the OneAuth bundle for the Facebook login; however, we continued to get errors.
Is OneAuth not compatible with Sentry?
Sentry is coming out with a socialplugin soon. Should we just wait for that or how should we go about this?
OneAuth author here, the problem right now is Sentry is not using Laravel Auth Driver to authenticate the user which make it difficult for the integration to happen. The two way to tackle the limitation:
Convert all Auth called in OneAuth to use Laravel\IoC, this would require Sentry to register IoC on their side.
Sentry to add an adapter class (extends Laravel\Auth\Drivers\Driver)
Either ways, there some works need to be done on Sentry side, I'm open for solution if they are looking to use OneAuth as their social plugin.