in the google wallet merchant center, if I click on one purchase I am taken to detailed panel where an "SKU" field is displayed along with item name and description.
While name and description are filled just as they were specified during the purchase (in the jwt), the SKU (aka item id) field is empty.
not surprisingly since it wasn't specified in the jwt.
not surprisingly since there is no place for it in the jwt specs.
so why is the field present in the order details in the merchant center?
is there any way to get the SKU to be present during the purchase?
Related
Is there any way to show active subscription plan on stripe's embeddable table, like passing customer, subscription or price id?
https://stripe.com/docs/payments/checkout/pricing-table
How on client side, where stripe pricing table is used, can be prevented for user/customer to select another (or same) plan and do any sort of action except updating current plan with upgrade or downgrade?
The pricing table product is built for first time purchases and it allows you to easily drop an iframe on your webpage that shows the different price options that you offer to your new customers. Once you have a Customer that has already made a purchase, the pricing table product is not what should be used.
Instead, separately, you can let your existing customers manage their subscriptions with the Customer Portal here which has a full Stripe redirect page. You can pass the list of Price ids when creating the portal configuration so your customers are able to upgrade or downgrade to different prices.
I have created a custom checkout for bigCommerce it's a third party app so I am able to create the customers and orders on the Bigcommerce portal but on the order page the country flag is not showing with the customer. Is there anything I am missing for the for order flag.
And also shipping method is not syncing with the orders.
You have to pass the geoip_country and geoip_country_iso2 with order parameters the country flag will appear with the orders according to the ip address.
I'm using Stripe Checkout. In all the documentation I can find, Stripe recommends saving Customer information (including a default Source) during my first transaction with that customer, and using that default Source later when I want to create subsequent Charges. However, if a customer uses a different credit card during a subsequent Checkout transaction, it would be a mistake to charge the default Source.
So, it seems like I should always just use the token from stripe.js when making subsequent changes, and that I should create a new source for the customer whenever I detect the them using a card that's different from the default source.
However, in my testing it appears as though every token I get from stripe.js represents a unique card, even if I've used the same credit card number, expiration, and CVC. If I were to create a new card for each Checkout token and save it to the customer record, I'd potentially end up with mounds of duplicate card records for each customer.
Am I overlooking a way to associate stripe.js tokens with customers in a way that doesn't generate duplicates? Or am I going about this incorrectly?
Whenever you collect card details in Checkout, Stripe will create a new token for that card even if they use the same card details. The Token resource has the fingerprint property though.
That property is a unique identifier for a given card number in your account. This means that if I sign up today with my card and then I come back tomorrow with the same card under a different email address you'd see the same exact fingerprint on both Token or Card objects. The idea then would be to keep track of all the card fingerprints you see in your database to detect a returning customer. Whenever a customer adds a new card you'd first look if you've seen that card fingerprint before in your database and decide to create the customer or return an error based on this.
Separately, you should not offer Checkout for a customer that already has a saved card. Instead you should show them the card(s) available for example by showing the card brand and last 4 digits. And then the customer can either pay with one of those cards or add a new one.
You can add more than one card to a customer or replace the default one. You can also decide which card to charge by passing both the customer id in customer and the card id in source. This is all covered in details in Stripe's documentation here.
In the DocuSign GUI it shows a number in the top right corner which I presume is the company account ID. If your user is in multiple company accounts then you can switch between these accounts and the number changes. My demo account ID's are 17107 and 1133955.
I cannot find a way to get this ID using the API. I need it because a customer has multiple accounts with the same company name and we need to show the same account ID to them so they can differentiate between the accounts in our GUI like they can in the DocuSign GUI.
With the Credential API I can get the list of accounts for the user but the account ID here is the API account ID which is a GUID, not an integer.
Using a simple Login API call you'll get a list of the user's accounts. Each of the loginAccount objects within that list also contains an accountId parameter.
Please see the documentation regarding the login_information REST API call:
https://www.docusign.com/p/RESTAPIGuide/RESTAPIGuide.htm#REST API References/Login.htm?Highlight=login_information
A number of my specials have no campaign details associated to it. However, to be able to post a page update in Foursquare it requires a campaign Id, therefore I am no longer able to post a page update with a special attached.
My Special ID is 50ab336490e745590ae17e57 and that I can pull its details via API call. But when retrieving list of all campaigns, the special doesn't exist/not associated to any campaign.
And Add a page update requires CampaignID
https://developer.foursquare.com/docs/pageupdates/add
Has there been a change in Foursquare API? Thanks, please help.
Make sure that you are making the request to the campaigns/list and specials/detail endpoint with the same user who created the campaign and special. This information is only available to the manager of the special.