I want to include debit/credit card payments powered by papal for my website, I am following the guide as per
https://developer.paypal.com/docs/business/checkout/advanced-card-payments/
but for the code
paypal.HostedFields.isEligible()
I always get the false or undefined as error, may be I skipped something, please help.
I found this answer on the Paypal community.
"In my case, I was using a personal account as a developer account. When I created sandbox credentials from the Business account it started to work. So make sure,
Developer account is linked/created with the business account
Sandbox account is created from that.
Sandbox account should also be a business account and it should be enabled for advanced payments ( Using this link: https://developer.paypal.com/docs/business/checkout/advanced-card-payments/#enable-your-account )"
Here the keypoints:
You need a business account to use advanced payments.
You don't need to have a real business account when working in the sandbox environment: you can create a fake business account in the sandbox and use it.
You need to ask for approval to use the advanced payments. This request must be done separately for sandbox and production accounts.
When loading the Javascript SDK be sure to not pass the disable-funding=card parameter, otherwise isEligible() will return false even if your account has been approved!
Related
I was testing Stripe APIs for Connect custom accounts, but for some reason, I keep getting pending verification. I tried to follow docs step by step, and I used testing tokens for account onboarding, created Person object, and uploaded testing files that need to be verified on the dashboard. Without verification, I cannot test payouts. I must have missed extra steps, but I was not able to figure it out. Does anyone know how to make it verified for testing?
I have one more question to make sure that I am not misunderstanding the custom account. Can the platform make a custom account have a direct charge instead of a destination charge? And if possible, is liability for returns and disputes still on platform?
You can check the account's requirements.currently_due hash, it tells you what information are needed to keep the account enabled. You should also use Connect Onboarding to collect the necessary info.
Technically you can create Direct Charge on custom connect accounts. However, it's not recommended. Because:
There's no Dashboard for custom account to address disputes
There's no Dashboard for custom account to set Radar rules
Refunds for Direct Charges on connected account will results in negative balance, which platform needs to cover
I have a small business where 5 of my customers use docusign. They want to be able to manage their docusign accounts through our website. I have created a docusign api on my end which I tested using my own developer account using my integration and secret keys which I store on my server in the db. I now want to allow my 5 customers to use this api to control their own docusing accounts. Do they all need to have a developer account and make it go live? I'm sure there is a better way and I cant make sense of it.
Do I need to push my app to live as well and purchase an API plan from docusign?
Please help it s hard to find any resource about this.
Do they all need to have a developer account and make it go live?
No, they don't need to. They have a production account and once your app goes live they can use your app with their account. If you want them to test your app in the developer environment first - then yes, they can get a developer account (which is free) to do some testing, but not required at all.
Do I need to push my app to live as well and purchase an API plan from
docusign?
Yes, you need to make your app live so that it can be used by paying customers in production. You would need your own production account to do that. If you are an ISV/Partner - you can get a free one, otherwise you will have to pay for your plan.
I am trying to integrate our web app with DocuSign. We expect our web app customers will authenticate and grant consent to our app to make API calls on behalf of their DocuSign accounts. Then our app will create envelopes (using access tokens to customer DocuSign accounts) and allow our app users to sign them using embedded signing.
We've built a prototype using demo account and everything works like a charm.
The only thing what is still unclear for me is how it is supposed to work after going live.
Am I right that our customer will be charged each envelop sending, since our integration makes call on behalf of their account?
Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?
Could anyone advise on the matter. Thanks!
Am I right that our customer will be charged each envelope sending, since our integration makes call on behalf of their account?
A. Yes, you're right. If your customer logins in to DocuSign using their own DocuSign user account, then their DocuSign account is charged. Your own DocuSign account is not involved, at all, in this scenario. Your client id (integration key) can be used by any DocuSign account user with their own account, once they grant consent to it.
Is it enough for our customer to pay for Standard eSignature Plan to make embedded signing work, or they should choose Enhanced Plans (the one where API feature is listed)
A. I don't believe that the standard eSignature plan includes support for embedded signing.
Should our account plan (which holds Integration Key) be at least Advanced Developer to support embedded signing?
A. Either Advanced Developer or a "regular" eSig account that supports embedded signing. This is for your testing purposes. If you use a regular account that supports embedded signing then your other company groups can share the account for use in sending out agreements for signature.
Also
Please sign up as an ISV with DocuSign via https://partners.docusign.com
(no charge.) Being a registered partner provides you with additional information and enables you to use the partner use license to sell your app to DocuSign customers.
Pro-tip: use your developer account to automatically test your app. Preferably once a day. New releases are first launched on the developer system about a week before production. DocuSign has thousands of tests to guard against regression bugs. But it is possible for a bug to slip through. If you detect any issues on the developer system then DocuSign will typically stop the production deployment to fix the issue.
Added
Re error message when a feature is not enabled: see this question.
Re which plans include the embedded signing feature: sorry, I don't have that information.
I am going to build an eCommerce website that supports PayPal.
Buyers connect their PayPal account to the website before they get products.
The website should collect funds without a normal checkout flow whenever buyers buy products.
For this, I've researched the Permissions Service API on PayPal.
But, I can't find enough descriptions to build such a website.
I would like to know how to integrate PayPal for this.
What you are looking for is a "Reference Transactions" solution. It can be tested in sandbox, but to use it in live, the business account would need to be approved for this feature by PayPal. To do this the account owner would need to contact their PayPal account manager or PayPal's general customer support (not MTS), and explain the business need for this feature.
As far as implementing the solution, the only public documentation I'm aware of is for classic APIs: https://developer.paypal.com/docs/classic/express-checkout/ec-set-up-reference-transactions/ . Any newer API or vault solution does not appear to be publicly available at this time, but you could always contact PayPal's support and ask if there's something they'd rather you implement than those classic APIs. The more significant hurdle is the business approval for the feature mentioned earlier.
I'm integrating google wallet with a php-game. I've come to the part where I want to test if my postback-script does it's job, but I can't seem to find any information on how to make a test purchase. I get this error when I try:
I'm in the sandbox so I don't understand why this is happening. Help?
Updated to encompass comments/discussion:
Create a new sandbox buyer account - aka a new Google Account/email address.
It's a dummy account so you don't provide real data nor real credit cards - re: use test cards
accounts must be distinct - you cannot use the same sandbox Seller/Merchant account for your buyer account (that is what the error is saying).
use a different browser (no pre-exsting/seller auth data/cookie) to test the purchase process using your buyer sandbox account (or if using Chrome open up an incognito window)
Hth.