Occasionally Yodlee will assign an incorrect merchant name based on description text for a transaction. For example, "APPLE RIDGE FAMILY MED" will come in as "Apple, Inc."
Is there a way to make a rule in Yodlee such that this does not happen? I know you can assign a new category, but Description/Merchant name doesn't appear to have something similar.
Currently Yodlee doesn't provide any API to do so but what you can do is file a Service request using Yodlee customer care tool about this problem and Yodlee's internal team will get this fixed.
Related
I am working with EBAY [REST API]. For this i am using SANDBOX [which is test enviornment of Ebay]. I have created a developer account and two sandbox test user.For acting as a buyer and seller.I am trying to create listing using seller account. i created the product in the inventory but when i publish offer it gives me error and i could not publish the offer. it give me error like create policies etc.
I want to create a product using seller account and then buy tht product using buyer account.
Is there any other way to create listing ?
I am following this : https://developer.ebay.com/devzone/guides/features-guide/content/basics/Call-SandboxTesting.html
Since you have not specified the exact error you are getting when making the publishOffer call, I will try to outline the whole process for reference. The prerequisite steps for publishing an offer from your sandbox account are:
Create Payment, Fulfillment, and Return policies for your sandbox account. For this, you may call their respective APIs or you can use their API Explorer which has sample policy requests ready to be executed or, easiest of all, you can manage your business policies from the sandbox website here
Create your inventory item using createOrReplaceInventoryItem call
Create an inventory location for the created item through the createInventoryLocation API call. Your offer won't publish without this.
Create an offer for the inventory item. Specify the offer details, such as fulfillment, payment, return policy IDs, category ID, inventory location ID, etc
Publish the offer
There are quite a few requirements, specific to the type of item you are providing through a listing, that you have to fulfill before eBay will let you publish the offer. You can find more information about this in the error response you get when publishing the offer.
With that said, eBay's sandbox has behaved very unreliably in the past from my experience. So if you are doing everything right and still running into problems, as a last resort, you can try creating the listing by using eBay's Trading API's AddItem call. I have personally found these sets of eBay APIs to be more reliable (albeit more outdated).
We ship using FEDEX and UPS, and we never found a need to post the tracking number to the payment record, however, recently a customer did a charge-back and the claim was that the order was not shipped even though it was. The tracking number was not entered into paypal, but we do have a tracking number for this order. Do we need to manually enter every tracking number into Paypal, or do we have a chance to enter it after a chargeback attempt has been made?
PayPal's standard API does not provide a field for tracking numbers in their order details, so there is no way to automatically send PayPal this information for all orders.
Their API supports disputes, so it could be possible, however it looks like it could be very messy. The workflow would look like this:
Use PayPal's Customer Disputes API to GET all disputes with a dispute_state of REQUIRED_ACTION and reason of MERCHANDISE_OR_SERVICE_NOT_RECEIVED. Save the Order ID
Cross reference the Order ID with your order management software's API to get a tracking number. If the tracking number exists,
Use PayPal's Customer Disputes API to escalate the dispute to a claim and save the returned claim API endpoint.
The documentation gets a little fuzzy here and may require some contact ith PayPal's support team, but it looks like you should be able to POST evidence to the claim with PROOF_OF_FULFILLMENT, which includes tracking_number and carrier_name.
Unless you are processing a high volume of these missing order claims it probably won't make sense to go through all this legwork. If it truly is taking a lot of time and energy for you or your staff to handle this specific type of PayPal dispute then maybe it would be worthwhile. I might also suggest in this case to start toggling the "signature required" settings for your shipping partners.
I signed up as an associate to use the API, but then when clicking the Product Advertising API, it did not let me sign up. I emailed to see how I can access it and was told this:
Registration for the Product Advertising API is only available to Associates that have been reviewed and received final acceptance in to the Associates Program.
Applications that are in the pending approval status will be reviewed once 3 referrals are made on the application.
I don't know what that really means, and I don't even necessarily want to be an associate; I just want to use this API to get Amazon search results for a browser extension. Anyone know how I can achieve this?
They added a new rule recently ! You can only use the Product API if you have sold at least 3 items.
I've tried to do this with a different account and credit card, but I still got 0% commission lol
and then you need to contact to amazon
This is my first attempt to use an API. I followed the instructions for registering for an Edmunds API (http://developer.edmunds.com/).
I registered for an account, got an email from them to confirm, clicked on that link, and got a request to register my application, which I filled out.
But when I log into my account and click on "keys", all I get is the message "You don't have any keys yet".
What am I missing? Thanks in advance.
Here is the email response I got from Edmunds:
Joe,
Thank you for your interest in the Edmunds Open API Program.
Unfortunately, we are in the process of retiring our Open API Program. Therefore, we are unable to issue you an API key at this time.
Regards,
Edmunds
UPDATE
The Edmunds API has been shutdown.
I would like to also recommend this website, it contains a list of the latest car information/database APIs.
I can't remember exactly how I created mine, I believe I created my dev account and then received an api key link via email. I clicked the link and it took me to a page where I could setup my app and receive an api key. You should have received said email by now.
If that doesn't work then try emailing: api#edmunds.com
An alternative to Edmunds API would be Marketcheck Cars API
The developer portal is given here with Comprehensive API documentation
The APIs supported are
Inventory Search API
VIN History API
Dealers API
VIN Decoder API
CRM Cleanse API
and lots more APIs coming up like - Market APIs with active and historical market averages, trends, dealer sales stats, dealer ranking, deal ranking, total cost to own, car market values (like Edmunds TMV) coming up
I tokenized a card with Balanced.js, and am attempting to create a buyer with the buyer email and the tokenized card URI. I'm seeing this error:
Balanced::Conflict(409)::Conflict:: POST
https://api.balancedpayments.com/v1/marketplaces/TEST-xxxxxx/accounts: cannot-associate-card: Cannot associate card with accounts on this marketplace. Your request id is xxxxxx
Any ideas on the source of the error and how to fix it?
Thanks!
This is usually an indicator that you're trying to associate a Card that was tokenized on one marketplace with an Account that exists on another marketplace. Cards tokenized in Balanced can only be associated accounts on the same marketplace.
The often happens if you're moving between test and production environments. The most obvious place to look is at the marketplace_uri parameter that you're passing through to balanced.js.
You'll see some code in your javascript that looks like
balanced.init(marketplaceUri);
That uri must be the same as the marketplace that is associated with the API key that you're using to process payments.
You need to change the api key
require 'balanced'
Balanced.configure('')
To find it go to dashboard > settings > api key secret