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.
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 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!
I want to create a platform which will provide a digital service where the customers and connected accounts will be from around the world. Clearly Stripe Connect is the Stripe product to use.
Because many of the connected accounts will be overseas this straight away rules out the use of transfers - unless I explored setting up separate platform accounts in the different overseas countries. (https://stripe.com/docs/connect/capabilities-overview#cross-border-transfers)
So I am left with destination charges where I choose the connected account as the settlement merchant via the on_behalf_of parameter. This means the charge goes against the connected account but I can still make money by charging an application fee.
As the connected account will be invisible to the end customer on the platform it seems inappropriate for the connected account's details to show on the customer's bank / credit card statement. Instead I want the platform's details to show.
Stripe support have assured me it is possible to have only the platform's details. Indeed this part of the API suggests I can control the statement descriptor which shows - https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-statement_descriptor
But another article - https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-statement_descriptor - seems to almost contradict this. It explains
Any additional information that’s displayed on a customer’s statement
is also provided by the same account that provides the static
component (business address, phone number).
Can anybody clarify? Many thanks in advance.
Update
This article appears to settle the matter - https://stripe.com/docs/payments/connected-accounts
Guess I will just have to inform users on my website with a connected account that their details will show on the bank statement.
I've subscriptions set up for Automated Recurring Billing (ARB) using customer profiles in Authorize.net.
I was able to create a subscription correctly but I'm getting transaction status as settlement error.
For transactions, I'm using test credit card provided by authorize.net and currently, I'm testing it using sandbox account.
Can anyone please tell me how to how can I test ARB in authorize.net?
Yes, You can.
Just change the Test Mode to Live mode in your sandbox account.
Now you can add subscribers by test card details into the ARB transactions.
We would like to know how we can test stripe in LIVE for an e-commerce website? The site basically is an e-commerce website and courses are purchased online, how do we test LIVE transactions without using real-time credit cards in stripe?
The purpose of Stripe test mode is to ensure that you get your code into a perfectly working state, and that each type of transaction you are dealing with is fully covered. You can even validate that WebHooks are working by pointing them at your application's test API endpoints.
There's not really a way of 'testing' inside of the live environment as such - typical practice would be to make a real transaction using a company credit card, or one that you are in control of. You can then logon to Stripe Admin and refund the payment once it succeeds.
This is the same with most payment gateways, although there are some that have test mode built into the live API, and used via a specific header, parameter or tracking identifier. Although, this is really just the same end result - you are still testing in test mode.
Use a 100% off coupon and no monies will be transacted. This should allow you to test the flow of things in livemode and make sure everything is in sync without posing a threat to Stripe as a company or your Stripe account.
Note: If you're testing a stripe subscription, you should immediately end the subscription, and delete the "customer" before you forget and it's ACTUALLY processed the next billing cycle.
Here's an example of creating and using 100% off coupons.
Disclaimer: I have NOT tested this method. But I believe my theory is correct.
You can use Customer Credit Balance (https://stripe.com/docs/billing/customer/balance) and use real credit cards to do some final testing of your live implementation. I just did it, it works perfectly and no charge is being done.
Good luck!
This can be accomplished from the Stripe dashboard in one of two ways. The set up for both methods begins in the same way.
Navigate to the Customers section of the Stripe dashboard, and create a new Customer object for yourself (or your employees)
Once you've created the new Customer, add the card details for the real card that you or your developers will using to test the live Stripe integration. This step is necessary because Stripe uses the card number to associate any test payments you make with the Customer you just created.
With the new Customer still selected, you'll see an Actions dropdown to the top right of the Overview page.
From here, you can select one of two solutions to waive costs for your new Customer:
Create a permanent 100% discount by selecting Apply Coupon and following the New Coupon link to create a coupon that can then be applied to your Customer's account
Create a credit balance for your Customer by selecting Adjust Credit Balance and setting it to a sufficiently high value
I recommend the first as it allows for more control. In particular, coupons can be set to never expire, unlike credit balances that will eventually hit 0 and require you to remember to reset it.
To prevent abuse or avoid creating an exploit for potential attackers, you can even set the coupon to be redeemed only as many times as you intend to redeem it, preventing it from being applied by anyone who doesn't require it to test your Stripe integration. In the below screenshot, I've set it to be one-time use.