I have created service to offer the brands to create appointment passes and send via email, brands can create passes and send notification using my service.
This service allows them to send push notifications and using their brand name Can someone suggest as per attached image it’s in conflict or not
.
This clause authorizes your customers to send you their certificates for your service to manage on their behalf. This is a good thing and what you want them to do.
If I read between the lines, I believe you are asking if your service can your own single certificate to send to multiple brands. Attachment 5 to the Developer Agreement states:
You may use the Pass Type ID only for purposes of digitally signing
Your Pass for use with Wallet and/or for purposes of using the APN
service with Your Pass. You may distribute Your Pass Type ID as
incorporated into Your Pass in accordance with Section 2 below only so
long as such distribution is under Your own trademark or brand. To the
extent that You reference a third party’s trademark or brand within
Your Pass (e.g., a store coupon for a particular good), You represent
and warrant that You have any necessary rights. You agree not to
share, provide or transfer Your Pass Type ID to any third party
(except for a Service Provider and only to the limited extent
permitted herein), nor use Your Pass Type ID to sign a third party's
pass.
This strongly suggests you should only use your certificate for passes bearing your own trademark or brand.
It's a grey area. Only you can really decide whether or not you want to risk having your certificate revoked.
Related
I am exploring tokenized payments on the web and I am slightly confused. The ApplePay JS class is first instantiated which triggers paySession.onvalidatemerchant = function (event) {...}. At that point event contains a validationURL which we need to send to our back-end in order to: Request a valid session from the Apple Pay server. My question is, as part of the steps of the setup, we need to declare all domains and sub domains displaying the ApplePay button; what about the server's domain that will authenticate with apple apis and request the session. Where are the declared domains where the buttons are displayed tied into the whole interaction.
Apple only displays ApplePay button when you use the same domain that is verified in the apple developer account.
And yes if you are using 10 domains/sub-domains to show the apple pay button then you need to verify those domains on the apple pay account.
For more information, you need to check the following documentation you will get all your answers. This documentation created for both professional and biggers.
https://gist.github.com/jagdeepsingh/c538e21f3839f65732a5932e35809d60
I'm working on an app that uses the Square API to react to Point-of-sale events. For example, a customer goes to a take-out restaurant. The restaurant uses Square to accept payments. The customer pays cash. At that point, Square sends a notification to a custom webhook with the PAYMENT_UPDATED flag. Then, the app I'm working on should send a push (APNS) notification to the device that just accepted the cash payment.
The problem is that I haven't found a way to single out a particular device within a Square location. So what ends up happening is that all devices registered to a Square account get the push notification.
The user registration workflow is as follows:
A business launches the app and gives permission to receive push notifications (this is where we get and save the device token).
The business registers for an account.
The business authenticates with Square (allows our app to receive Square notifications).
I feel like there should be a way to associate a device token used for APNS with a device ID linked to a Square Location (and subsequently accessed via Square's Location API), but I haven't been able to figure it out.
Any thoughts or suggestions? Thanks!
UPDATE
The code isn't really the issue. By that I mean whether we're using PHP, Java, Ruby, etc, the issue remains the same. The only solution I can think of would be to use Square's SDKs to build a completely custom POS system, but that'd be like using a sludge hammer to put a tac in a wall.
The ultimate goal is to simply create a relationship between a Square device and a user's device I have stored as a record in my sql database. Seems like it should be straight forward, but not so much.
edit:
tl;dr: you can't.
You have to create a payment method in order to verify it. Creating a sale does NOT invoke verification, even if verification is enabled globally.
original:
I'm reading about credit card verification, which apparently isn't done automatically during Braintree_Transaction::sale(), but I don't see any options to enable verification on calling sale().
Do I really have to implement (at least) two separate API transactions just to verify a credit card?
Ideally I would like to use a single call to ::sale() to perform validation, authorization, and capture.
I have already enabled verification through my control panel, and I'm using test credit card number 4000111111111115 which, is supposed to be declined, but i'm getting successful transactions with it.
Do I have to create a payment method separately in order to perform validation, even if I have global validation enabled?
Full disclosure: I work at Braintree. If you have any further questions, feel free to contact support.
To test card verification results, please adjust the amount of your transaction. Because these cards are not linked to real accounts, Braintree cannot make the small authorization charges that are made in production, and instead the API must rely on the amount of the test transaction to dictate the expected response.
In a Production environment, Card verification is triggered by the creation of payment methods, not by transactions. To enable verification, either enable it across all payment methods, or add the verifyCard option to your PaymentMethod::Create call. The response to PaymentMethod::Create in either of these cases will contain a creditCardVerification object if the verification fails for any reason, allowing you to stop the transaction before sale is called.
From what I see, Bot Framework is providing an abstraction over users in different channels by providing a ChannelAccount class that has ChannelId/Address pair to identify user via its account and Id property, which is... okay, here's the question.
I suppose that the idea behind Id is to provide a unique and persistent identifier that can be used to cross-correlate users between account (i.e., I can say that Slack user #alpha is also email user alpha#company.con). This idea is supported by the fact that ChannelAccount for my bot always has same Id regardless of the channel (and Address is different between channels, obviously).
If this is right, and I hope it is, is there any way to provide BotConnector with the correlation information? I.e., I want BotConnector to give me ChannelId/Address, and I'd give back user Id which I'd the get back in incoming message.
The purpose of this is quite simple: I want the code inside my bot to use the Id as already correlated identifier so that I can log it, build logic from it and so on.
BotFramework does not yet support linking of accounts. In the interim, take a look at this post for one way you might implement a solution:
Why isn't BotUserData persisting and retrievable in my Bot Framework bot?
Is getting label using USPS api such as "USPS TRACKING (https://www.usps.com/business/web-tools-apis/usps-tracking-v3-3.htm)" any different than postage paid label obtained from 3rd parties such as endicia.com, stamps.com?
Is it possible to purchase prepaid postage on usps.com website, then calling the USPS label api to generate postage paid label? I mean when we call the API to generate the label, appropriate amount to be deducted from my USPS account.
I dont understand the use of the label generated by USPS API. I mean, I have activated my account at USPS and now working on production server. Now if I generate any label using the API (https://www.usps.com/business/web-tools-apis/usps-tracking-v3-3.htm), and generate a label. I didn't see any data in my history at online account. I mean, this generated label is of no value? or still my account is not activated? as I think, i have not yet done this -
reference pdf:Development-Guide-v3-1d.pdf
Step 7: Receive Printer Approval from ICCC Implementing the Delivery
Confirmation and Electronic Merchandise Return Service with Delivery
Confirmation APIs requires this additional interim step. The NCSC will
review your labels within two business days. If the labels fail the
certification test, the NCSC will contact the person listed on the
submission form directly. If the labels pass, you will be notified by
the Internet Customer Care Center and you will be able to send XML
transactions using your “live” data and receive “live” responses. Once
you are approved to generate “live” labels from the production server,
and you need to print additional test labels for any reason, be sure
to use the “Sample” XML request. Otherwise, the USPS will send a
manifest of the PIC numbers issued to the USPS Postal Tracking System
and will be looking for the Delivery Confirmation labels to scan.
Does, receiving "Printer Approval" will solve my issue?
Answers to your questions are below:
It's different in that you're ordering through a 3rd party provider, but not different in that you're paying the same amount for a shipping label, and that shipping label has a value and can be used in the USPS system. This holds for Stamps, Endicia, and other 3rd party API integrations like Easypost
You should be able to do that entire action through the API.
Did you check back on your account? This information should definitely update in your account. Unless you are using an API key that's tied to a different USPS account?
Let me know, happy to help further.
If you want an api that prints postage, use Shiprush or another developer tool that is made to generate complete, ready to use shipping labels.
Labels generated using the API DeliveryConfirmationV4 do not include postage. Per the documentation,
Please note that the API labels are printed without postage. Postage
must be purchased and applied separately.
See https://www.usps.com/business/web-tools-apis/delivery-confirmation-domestic-shipping-label-api.pdf