I am trying to integrate Authorize.Net in WooCommerce, using the following plugin for it: https://wordpress.org/plugins/yith-woocommerce-authorizenet-payment-gateway/
I set all user IdTransaction Key md5 Hash, but it gives me error 87, I don't understand where I need to put x_market_type as per the support document said.
This is the error I am getting:
From the Authorize.Net documentation about error code 87:
Response Reason Code: 87
Response Reason Text: Transactions of this market type cannot be
processed on this system.
Notes: The server is not configured to process the product type
derived from the market type of this transaction.
This can happen for four reasons:
You are attempting to process a type of transaction that your account
is not designed to process. For example, you attempt to use a card
swipe machine with an account that is enabled for Card Not Present
transactions.
Your software integration is passing an incorrect value
for the field x_market_type. If you are using a Retail account,
x_market_type should be set to a value of "2". The integration guide
for Card Present transactions can be found at
http://www.authorize.net/support/CP_guide.pdf.
Your Merchant Service
Provider may be incorrectly set up for this account.
The product type
(SIC code) is incorrect for this account.
It is recommended to check
the posting URL that is being used for your integration. Please
consult the guide for the integration method you are using to verify
the correct posting URL.
To help troubleshoot this issue, you can confirm the Product Type for
your account using the following steps:
Log in to your account at https://account.authorize.net.
Click Account from the main toolbar.
Click Merchant Profile.
Refer to the Product Type listed under Business Information.
Related
I'm trying to create a simple subscription payment on sandbox PayPal.
I have a business account on sandbox, with which I have created a subscription plan.
Furthermore, I have a test user on sandbox with a credit card generated here: https://developer.paypal.com/api/rest/sandbox/card-testing/
Everything works fine but when I get to the payment confirmation I get this message: "Sorry, cannot use your chosen payment method to set up subscription item. Please try other payment method"
I tried using other cards or creating another test user but I always get this same error.
I've also posted the question in the paypal community but didn't get any response: https://www.paypal-community.com/t5/Sandbox-Environment/Subscriptions-payment-declined-because-test-card-not-working/m-p/3023752
Second problem: When i make a simple payment it works fine, but when I try the pay in 4, it tells me to setup a card (even though I already have a card setuped) and when I try to resetup it on the payment modal I get the error : "We cannot process your request at this time. Try again later."
I thought maybe if I add credit to my test account I can bypass this. But when I go to the page to add credit (https://www.sandbox.paypal.com/myaccount/money/addmoney/topup) it's blank and there are errors in the console.
So I tried to send money to me test account from another account and it doesn't work either...
I was wondering is there like an option or something I have to activate or disable in the settings so my test will work, or is the PayPal sandbox environment just bugged ?
If you need anymore informations or details don't hesitate to ask, I'm not sure if my explaining was clear.
Create a new sandbox personal account at https://developer.paypal.com/dashboard/accounts . Use that account to test the subscription.
The result of Pay in 4 payments is a PayPal payment. You can already test PayPal payments without Pay in 4 as a funding source. So, do not test Pay in 4 in sandbox. There is no reason to.
I'm trying to use the Share API in Linkedin in order to retrieve posts from an user.
https://learn.microsoft.com/en-us/linkedin/marketing/integrations/community-management/shares/share-api#find-shares-by-owner
I get the following error making the call:
Field Value validation failed in PARAMETER: Data Processing Exception while processing fields [/authors]
status:403
From all my digging I saw that probably I need r_member_social permission, but there is no way I can see how I can get that for my application.
Can anyone guide me how I can get that for my application so I can retrieve one's shares with some statistics.
Thanks
Scenario
I'm using paypal sandbox account for payment right now and I've set it up correctly , the order is getting successfully placed if I use paypal payment while checkout. But the status should be completed but its not assigning that.(I'm trying this with virtual product only)
I've already read several articles related to same issue and I only found that if it is set properly then the status should be completed or either I've to set it manually by using code(but is this only way? and is it proper?).
Following are the observations from admin side:
On Order Notes -
Payment pending (unilateral). Order status changed from Pending payment to On Hold.
Paypal log(only last 3 lines as it was huge) -
2019-03-08T11:40:45+00:00 INFO Received valid response from PayPal
2019-03-08T11:40:45+00:00 INFO Found order #9985
2019-03-08T11:40:45+00:00 INFO Payment status: pending
The typical cause of this is a mismatch between your paypal details.
When you signed up for Sandbox Paypal you we're given a sandbox email address. You must make sure you're using your Sandbox email and not your standard Paypal email address.
You can also try looking in
Woocommerce > Settings > Products > Downloadable Products
And make sure you have the grant access after payment box ticked.
http://cld.wthms.co/ZExhMq
In my case, it was happening because I had created both facilitator and the buyers account separately via https://sandbox.paypal.com in contrast both of these accounts should be created in https://developer.paypal.com > sandbox > accounts.
When I had created the account separately the email address was not getting verified, I think that could be the reason for it not to work also when the user accounts are created from (https://developer.paypal.com > sandbox > accounts) you can see notifications for each account and perform an action accordingly.
From my understanding of the regular WSO2 API Manager product I could create multiple synapse-configurations and register them as (global or api specific) sequences by placing them in the proper directory.
I would then utilize the Sequence configuration capabilites on the "Manage screen" to apply different sequences to the request and response payloads of the backend.
I read the documentation at https://docs.wso2.com/display/APICloud/Key+Concepts#KeyConcepts-Sequences as it is not possible to add more but I wanted to ask specifically.
Is it at all possible to do this type of manipulation in the current version of public API cloud?
I have talked with the relevant teams and this is how you can add a sequence in the API Cloud. Although I mentioned about adding a sequence via the Gateway's carbon console (and said it was broken), WSO2 API Manager product is not a position to make it working (this is a known limitation). If I explain the reason in simple terms, to support it they will need to ship a lot of mediator UIs which will make the product similar to the WSO2 ESB. Following is what you can do.
Use WSO2 Developer Studio to create the sequence you want.https://docs.wso2.com/display/DVS371/Creating+ESB+Artifacts#CreatingESBArtifacts-Workingwithsequences
Go to API Gateway at https://gateway.api.cloud.wso2.com/carbon
You need to login to the gateway. Username is email#tenantDomain. If your email abc#gmail.com and tenant domain (or the organisation key is xyz) you need to give abc.gmail.com#xyz as the username (note the # in the email being replaced with a DOT). Go to "Manage" in the top level menu of API Cloud and you will be able to figure out your organisation key.
Go to Resources -> Browse menu and navigate to /_system/governance/apimgt/customsequences/ registry path. Upload your sequence to in, out or fault folders based on your requirement. This will be then available when you create APIs via the API Publisher.
Yes, it is possible. You have to follow the below steps.
Go to API Gateway at https://gateway.api.cloud.wso2.com/carbon
You need to login to the gateway. Username is email#tenantDomain. If your email abc#gmail.com and tenant domain (or the organisation key is xyz) you need to give abc.gmail.com#xyz as the username (note the # in the email being replaced with a DOT). Go to "Manage" in the top level menu of API Cloud and you will be able to figure out your organisation key.
After login, you can go to sequence menu and add a sequence. I tried these steps just now and realised there is a broken page at add sequence. We are in the process of fixing it. Will keep you updated.
Difference of API Cloud and API Manager standalone version is, you have to store the sequence in the registry for it to be available at the API Publishing time.
We'll be adding a doc on this at the following location soon.
https://docs.wso2.com/display/APICloud/About+WSO2+API+Cloud#AboutWSO2APICloud-CommonAPICloudusecases
I want to find out profile's previous employment details. I have tried as per the LinkedIn's API given below.
https://api.linkedin.com/v1/people/id={id}:(id,first-name,last-name,headline,picture-url,public-profile-url,industry,three-current-positions,three-past-positions,positions)?format=json&oauth2_access_token={tokenvalue}"
Here in above request, "id" is 1st degree connection. Then also I am never returns with the desired information after tried many times.
Can any one guide me what should I do?
Regards,
Dharmesh Solanki
LinkedIn says here that it only supports retrieving the r_basicprofile fields from an application.
https://developer.linkedin.com/documents/profile-fields
For members other than the ones using your application, you may only
retrieve the profile fields available with the r_basicprofile member
permission.
Since three-current-positions and three-past-positions is part of the Full Profile (r_fullprofile), I don't think it's currently possible to get those fields for a user using the Profile API.
Unless it's for the current requesting user, ie:
https://api.linkedin.com/v1/people/~:(id,first-name,last-name,headline,picture-url,public-profile-url,industry,three-current-positions,three-past-positions,positions