Would like to integrate the amazon pay in the application(US based). Already having paypal and pay by card option.
When referred for amazon pay sandbox, it says to register in amazon pay first. The registration process is taken to amazon seller center account other steps where business related questions are asked.
In development point of view, how can we integrate the amazon pay to our application? Is there any sample api/code available and its procedures?
Any guidance is appreciated.
The official documentation on developer.amazon.com is a good starting point for the integration. The following link points to the US version of the documentation and provides links for the integration into websites and Alexa skills:
https://developer.amazon.com/docs/amazon-pay/intro.html
It also provides links to additional developers resources such as API Reference Guides, SDKs and sample code:
Related
We are building a video call application utilising Amazon Chime SDK. Our application serves customers in the UK and need to be GDPR compliant.
Amazon Chime's compliance info page doesn't explicitly state anything in relations to GDPR compliance. However AWS itself states it is, and Chime is a service under AWS.
So we are not sure if Chime itself is GDPR compliant. Could someonese please advice if have any relevant information to confirm or deny Chime's GDPR compliance conclusively.
After multiple attempts we did get a response - albeit vague - from AWS.
At the foundation of Amazon Chime security is Amazon Web Services
(AWS) Security. AWS regions and networks are built and operated to
meet the requirements of some of the world’s most security-sensitive
organizations. AWS constantly undergoes third-party audits by a
variety of public sector and private sector auditing organizations in
order to maintain its status under multiple compliance offerings, such
as the credit card industry’s PCI DSS Level 1, the U.S. Government’s
FedRAMP program, C5 Certification in Germany, and IRAP assessment by
the Australia Government. For more information, see the AWS Security
and AWS Compliance websites. Amazon Chime is designed and operated
according to the same AWS standards, has undergone the compliance
process required to be a HIPAA-eligible service, and is currently in
the process of being added to other relevant compliance programs.
The Amazon Chime SDK can be used by customers who incorporate GDPR
best practices and compliance using our Shared Responsibility Model.
So they seem to imply it can be used in a GDPR compliant way.
Additional info: Specific to chat feature, AWS advised us to use the data-messaging API route to ensure the data relay and retention within EU.
All chat messages in the Chime app are relayed and stored in us-east-1
(Virginia). The chat messages always leave the UK.
There is a data messaging API in the SDK that can be use to build
chat.
(https://aws.github.io/amazon-chime-sdk-js/modules/apioverview.html#9-send-and-receive-data-messages-optional)
These messages flow through the same region that is used to host the
meeting (London, for example) and they are persisted there for a few
minutes and until the end of the meeting so that they can be relayed
to other participants during that meeting.
I believe Amazon Chime is not GDPR compliant. The website provides no way to export existing user data. The documented approach to exporting history is to scroll back in the chat history and copy paste:
https://answers.chime.aws/questions/629/how-can-i-save-all-the-data-from-a-chat-room-or-co.html
Talk to your AWS technical POC. I am sure they can help you understand this better. AWS is a big ecosystem of services. Chime used with other services can be made GDPR compliant.
For instance, all Chime events are tracked via AWS EventBridge. Should be pretty easy to attribute and track all data for a specific user.
I'm trying to figure out which open source framework to use to start building a conversational AI for our business. We are a financial technology company so security/ privacy is just as important as ability to build features quickly.
Amazon Lex seems to be a good choice, is it possible to use it with Google Home or other voice assistants?
Also, any additional advice on which platform to use/ architecture would be very much appreciated.
Thank you!
Yes Amazon Lex can work with other services. From the Lex website:
"With Amazon Lex, you can build, test, and deploy your chatbots directly from the Amazon Lex console. Amazon Lex enables you to easily publish your voice or text chatbots to mobile devices, web apps, and chat services such as Facebook Messenger, Slack, Kik, and Twilio SMS. Once published, your Amazon Lex bot processes voice or text input in conversation with your end-users. Amazon Lex is a fully managed service so as your user engagement increases, you don’t need to worry about provisioning hardware and managing infrastructure to power your bot experience."
The answer is a bit more complex than that! Adding a bit more here as this is coming up in Google searches:
Yes, it can integrate with Facebook Messenger, Slack, Kik and Twilio SMS — those have options direct in the Lex interface for linking those services. When it comes to Google Home, you'd need to create your own bridge between Amazon Lex and Google's Actions SDK.
So you'd take what the Google Actions SDK hears someone say when they speak to their Google Home (the fulfilment text), and then need to pass that onto Amazon Lex. To do that, you need to use Amazon Lex's postText or postContent functions (Lex Runtime docs on that). I haven't done this myself just yet, but I've heard of others doing similar and spotted this Stack Overflow post explaining it in a bit more detail when looking for an example.
I try to integrate our test system with SagePay. But I've found lot of different apis and documentations for integration. I'm bit confused about it. Could you tell me which api version is most up to date and suits my needs?
I want to have recurring payment functionality without CVV resubmit.
System will be designed to work on US market.
This api have functionality which I want and it's also mentioned in some answers on stackoverflow
https://test.sagepay.com
This api is very easy to use, but I don't see recurring payment functionality (only with CVV resubmit)
https://developer.sagepayments.com
There is another set of documents for integration, based on .vsp services
www.sagepay.co.uk/support/integration-kits-protocols-document
I suppose some of those apis are legacy and are maintained for some old integrated systems. It would be great if documentation for those apis were gathered in one place and explained.
Sage Pay UK and Sage Payment Solutions(US) operate independtly to each other with different integration methods and API's. www.sagepay.co.uk/support/integration-kits-protocols-document relates to Sage Pay UK only.
As per Wikipedia:
SnapLogic is a commercial software company that provides Integration Platform as a Service (iPaaS) tools for connecting Cloud data sources, SaaS applications and on-premises business software applications.
It is surely a competitor to informatica, but it doesn't seem to be just another ETL tool. I have a rough understanding that it is used for data integration but that's about it.
Is it merely an ETL tool or does it have any other functionality? Also, what are iPaaS tools in general?
Well, the best place to learn about SnapLogic will be their website, https://www.snaplogic.com/
Here is a video of SnapLogic: https://www.youtube.com/watch?v=KYJK7bjOlA0
A simple developer friendly example:
Let's say i want to search for twitter feeds posted with a particular hashtag by a particular person and write that data into a database of my choice or into amazon S3. SnapLogic allows me to do that without learning about the Twitter API and AWS. SnapLogic takes care of the abstraction for the user so that they can focus on the business logic of things.
The demos are available in the blog: http://www.snaplogic.com/blog
A look at SnapLogic on crunchbase is not a bad idea and you could also find their competitors there.
Your other questions like what are integration platform as a service(iPaaS) tools is too basic and should just be googled.
Basically there are two types of cloud integration, iPaaS and dPaaS
Basically SnapLogic is a iPaas Tool (Integration Platforma as a Service), One of the growing online cloud based integration ETL tool.
As per the Gartner report one of leader in "Enterprise Integration Platform as a Service" refer below link
https://www.snaplogic.com/press-releases/gartner-names-snaplogic-as-a-leader-in-the-magic-quadrant
About tool and few useful links,
1.Designer
It's a canvas area to play and develop your integration pipelines.
2.Manager
Is is a main important to manage all the projects , pipelines, assets ,accounts,creating users and providing permissions, and also import and export of
projects.
3.Dashboard
Monitoring the pipelines logs and information of running pipelines and history.
Useful links:
1.Main site:
https://www.snaplogic.com
2.SnapLogic free trial:
https://www.snaplogic.com/free-trial
3.SnapLogic Documentation
http://doc.snaplogic.com/
4.SnapLogic Community
https://community.snaplogic.com/
5.SnapLogic Blog
https://www.snaplogic.com/blog
Also recently they released SnapLogic Extremem, Please have a look
https://www.snaplogic.com/press-releases/introducing-snaplogic-extreme-to-help-data-engineers-operationalize-cloud-based-big-data-integrations
I have implemented plugin for google checout payments but now i see the notice on google developer documentation that google checout is no longer available from november instead they released Google Wallet.
My question is :
Is Google checkout and Google Wallet API same or i will have to change the API for google wallet ?
Google Checkout has been retired and will be shut down on November 20, 2013. You will have to change your integration. The announcement below has more details and options for migrating your payment processing:
http://googlecommerce.blogspot.com/2013/05/an-update-to-google-checkout-for.html
Different new Google Wallet APIs (such as Wallet Instant Buy or Wallet for digital goods) are available that allow you to accept online payments for physical goods, digital goods or services. A list of the available APIs and documentation is at:
https://developers.google.com/commerce/wallet/
Also see this answer for a good explanation of the differences between the Instant Buy and digital goods APIs.
I got answer from Google Developer.
I have contacted them and they told this are totally different from each other and they will released new API for wallet as soon as possible. :)
They are obviously different - otherwise there would be no point in the transition but there may/should be a fair amount of overlap between the two APIs. Some good places to start looking at the differences is here and via the Android Studio.