I'm using Spartacus 2.0 front end as angular 9 so here my question is, can we edit the billing address for the specific credit card card and edit the saved credit card? Does Spartacus support the editing of the payment method? And by default we are using cyber source for payment process.
Unfortunatelly you can not edit existing credit card, you can only delete and add new one while checkout. Spartacus doesn't support it due to good e-commerce practices (it is discouraged). If you really need that feature, I can see API looks like ready for PATCH operation. You can check it in POSTMAN and implement if it works.
Related
I am creating a website where I would like the users to be able to create a profile, and choose to either sell or purchase items. My question is, like the title states, how would I allow my users to pay each other? Is it possible with paypals button feature? It is for a project so it doesn't need to be perfect, but I would like it to be safe.
The simplest integration of PayPal Checkout is https://developer.paypal.com/demo/checkout/#/pattern/client ; you will need a live ClientID for live payments.
Payments can be directed to a specified email address by adding a payee object in the purchase_units, documented here.
I am building a school application that will connect parents to teachers, i am using Ionic 3 and Laravel 5.6.
And i want to be able to send a notification to all parents, when for instance a teacher gives an assignment, when the teacher enters the assignment question and click on the send button, the question is save to the database, after then a notification should be sent to the mobile devices of all parents who's children are taking that subject.
I have done a lot of research on how to do this, on the Cordova Push Notification Plugin and Cordova Local Notification. I have followed a video tutorial that implements Firebase and Push Notification, and also One Signal and Push Notification. But i was still unable to achieve what i wanted.
If they are anymore materials out there, that could help me achieve this, I will be so grateful to have someone share it with me, or if anyone can help me out with is, I will be very happy.
These are the other materials I found:
The PHP Package repository
Laravel Notification Channels
Quora
Please let your users know that using OneSignal's "free" service would allow the company to get users data and sell it to others.
Google's Firebase cloud messaging service is reliable but comes with a cost if you want many connections. See Firebase Pricing Plans.
I personally used fcm. It was not really a breeze implementing it on my thesis but it worked nicely. No need to make the app listen on background for incoming notifications then create a local notification, me not selling my users data, and not paying anything on the use of firebase's services. I used the free 300 dollars gift from google cloud to shoulder the expenses from the firebase spark plan.(free for 12 months)
A warning if you use the cordova plugins of fcm: If you have a cordova plugin that uses google's services it may come in conflict with the fcm plugins you listed above due to different versions used. It may need manual editing on the src plugins.
If you decide on using fcm, this link might help you.
The basic steps you have to do after you set up the needed environment is to
Get FCM token on platform.ready async.
Save it to firebase under the said user
Create a cloud function that will send notifications
I want to dive into SendGrid (GoDaddy SMTP is sh*ty).
But I don't understand the difference between the Free plan and Lite plan.
Of course, Lite plan is really cheap, but seems to have less features than the Free plan, which is... free.
I first told myself that the free plan most be a trial (with limited time). But the website says "No credit card needed, no expiration."
So why does somebody would prefer the lite to free?
Bonus question : The only feature I need is something like a "Send Folder", so I can be sure all emails have been sent. Does both plans have this?
Update: the Lite plan no longer exists.
The Lite plan is for people that want to pay purely based on the number of emails sent. It has a limited feature set as a result. The free account has all features and has no expiration. Someone might choose Lite instead of Free because they want to send more than 12,000 emails/mo but don't need all the credits or features in the $9.95 plan.
SendGrid doesn't store any email content, so there isn't really a "sent" folder, but you can see a report of the last 7 days of email event activity by clicking on the "Activity" item in the navbar. Additionally you can have all this data pushed to you in near real-time via the Event Webhook, and very soon you'll be able to pull via API as well.
Myself mendy, i am designing web application, The business required to integrate payment gateway. I searched on site regarding the flow but i could not get much info on MSDN. I want to make payment gateway using SSL and 3rd party merchant account. How can i do it ? some info regarding payment gateway could guid me to start developing the component.
You'll need to hook up with somebody like PayPal to process your payments. They will provide you with documentation and possibly a library to access their service.
Note that your payment processor is not necessarily the same company as your merchant account.
I'm assuming you wish to integrate with a payment gateway, not write your own?
If so, the answer is that it depends on the gateway that you intend to use. Each has their own API.
We use Iridium Corp for our products in the UK - they provide a bunch of .net components that you can just call from your code. Paypal will provide a well-documented API. So will some of the other big ones.
If you want some tips, you could look at some of the open-source shopping carts, which all have code to integrate to many of the big payment gateways.
Hope that helps...
Jake.
You should give wepay.com a try. There is now a C# SDK available with a few example here: http://bradoyler.com/post/29357874298/wepaysdk
Not sure if the title is quite right for the question but I can't think of any other way to put it..
Suppose you wanted to create multiple different web apps, but you wanted a user who was logged into one app to be able to go straight to your other app without re-logging in (assuming they have perms to look at the other app as well). If I'm not mistaken, if you're logged into gmail you can go straight to your iGoogle, googleReader, etc without re-logging in (if you set it up right).
How would you approach this? What would you use? Assume the apps already exist and you don't want to change the initial login page for the users.
What you're looking for is called Single Sign On. If you follow the link you'll find several implementations.
Open ID as others have mentioned is not such a scheme as it requires a seperate login for each site. Open ID is merely a shared authentication system.
You would issue a cookie against foo.com, which would then be visible on app1.foo.com, app2.foo.com.
Each application can then use the cookie to access a centralised authentication system.
Try CAS it should provide the features you are looking for.
What you want is a single sign-on (SSO).
There are two approaches to solving this problem:
Roll your own implementation. In its most trivial form it can be implemented by the first site setting a cookie that holds the ticket for the logged on user and the second site verifying that ticket and accepting the logged on user. There are quite a lot of potential pitfalls here:
you have to protect yourself against information disclosure - make sure that the ticket does not contain the actual user credentials
you have to protect yourself against spoofing - a man in the middle stealing a valid ticket and impersonating one of your users
and others
Adopt a third party SSO mechanism. Google, Microsoft, Facebook and other big companies allow integrating with their identity providers, so that your users could log on to their website and they handle verification, ticket issuing and so on. There's also OpenID, which is an open protocol you can use to enable SSO on your site through virtually any identity provider that supports OpenID. The potential drawback here is that somebody else controls your access to your user identity and can limit the features you can offer and data you can mine for your users.
As mentioned you can use something like OpenId or similar to make the process simple. Otherwise if you roll your own you could use a cookie to store the login, then basically ALL applications must have an entry point that mimics the base url.
Google for example uses mail.google.com to as a pipline into Gmail which allows it to read a cookie stored with the google.com domain.