Google Pay on Android fails with Request Failed (OR_BIBED_07)
Request FailedShort answer
OR_BIBED_07 is a registration or access error, not a card error. Google lists three messages under it: Google Play services on the device is too old (8.4 or newer is needed), no encryption key is registered for the merchant profile, or the merchant profile has no access to the feature because production access was never completed. Read which message you got.
Fix it fast
1Find out which cause you have
Open the Google Pay troubleshooting list for this code and match the message your device shows. Also confirm which environment the app runs in, because test and production behave differently.
adb logcat -s WalletMerchantError2Match what you see, then jump to its fix
- 1
The message says the API requires Google Play services library version 8.4 or newer.Google Play services on the device is too oldFix - 2
The message reads No keys found for this merchant profile.No encryption key is registered for the merchant profileFix - 3
The message reads This merchant profile doesn't have access to this feature.The app has not completed Google Pay registration for productionFix
- 1
What does the error look like?
Request FailedAn unexpected error has occurred. Please try again later. [OR_BIBED_07]
Cause 1 of 3
Google Play services on the device is too old
1Check
Look at the Google Play services version on the device or emulator image.
adb shell dumpsys package com.google.android.gms | grep versionName2Fix
Update Google Play services on that device.
# Play Store > Google Play services > Update3Verify
Run the payment sheet again.
adb logcat -s WalletMerchantErrorConfirmed by developers.google.com
Cause 2 of 3
No encryption key is registered for the merchant profile
1Check
This happens with a DIRECT tokenizationSpecification, where you decrypt the payment token yourself. Google needs your public encryption key on file.
grep -rn "tokenizationSpecification\|\"type\": \"DIRECT\"\|PAYMENT_GATEWAY" app/src2Fix
Register your public key in the Google Pay & Wallet Console.
# Google Pay & Wallet Console > register public encryption key3Verify
Retry the payment.
adb logcat -s WalletMerchantErrorConfirmed by developers.google.com
Cause 3 of 3
The app has not completed Google Pay registration for production
1Check
An app that uses the PRODUCTION environment must have finished Google's production access request.
grep -rn "ENVIRONMENT_TEST\|ENVIRONMENT_PRODUCTION" app/src2Fix
Complete the production access request in the Google Pay & Wallet Console: finish the merchant profile, submit your app with screenshots of your test integration for approval, and wait for the response. A production build must also be signed with a release key; the debug key does not work in production.
// Kotlin: use the test environment while developing
WalletConstants.ENVIRONMENT_TEST3Verify
Retry the payment on the build with the right environment.
adb logcat -s WalletMerchantErrorConfirmed by developers.google.com
How do I stop it coming back?
- Keep the test environment until Google approves production access.
- Keep one checklist: Play services version, key registration, gateway parameters, environment.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Payments
firebase deploy fails because the Stripe client has no API key
Neither apiKey nor config.authenticator provided
The Stripe client is built from a key that is empty at that moment.
3 causes, each with a fixPayments
Metadata you set on a Stripe Checkout Session is empty when you read it
event.data.object.metadata.order_id is None in the webhook handler
Stripe does not copy metadata between objects on its own.
3 causes, each with a fixPayments
Stripe Elements shows console warnings or errors in a Next.js checkout
Could not find Elements context; You need to wrap the part of your app that calls useElements() in an <Elements> provider.
Most React Stripe.js warnings come from four mistakes: calling loadStripe inside a component, using useStripe or useElements outside the Elements provider, using the objects before they have loaded, and a Content Security Policy that blocks js.stripe.com.
4 causes, each with a fixPayments
Stripe says No such checkout.session when you retrieve a session
resource_missing
A resource_missing error means the ID is not visible to the key you used.
3 causes, each with a fixPayments
Stripe says there is no such token when your server uses it
livemode_mismatch
Stripe answers with a missing-resource error when the ID you send does not exist for the key you use.
3 causes, each with a fixPayments
A payment method is missing from the Stripe Payment Element, or the call to exclude it fails
Excluding apple_pay, google_pay or link with excluded_payment_method_types returns an error
With automatic payment methods, Stripe decides which methods the Payment Element shows.
5 causes, each with a fix