#n0ah_unexpected
1 messages ยท Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- n0ah_unexpected, 37 minutes ago, 34 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1249796042346463263
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
hi @wicked comet
Why was our ticket closed?
would like to continue the conversation
Hello again! We help in realtime on Discord, and close idle threads. If you want async or long-running support you can contact Stripe support via email: https://support.stripe.com/contact/email
This is the code we use to show the WebView:
<head>
<meta charset="utf-8" />
<title>Crypto Onramp</title>
<meta name="description" content="A demo of hosted onramp" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<script src="https://js.stripe.com/v3/"></script>
<script src="https://crypto-js.stripe.com/crypto-onramp-outer.js"></script>
<script type="text/javascript">
document.addEventListener("DOMContentLoaded", function() {
const stripeOnramp = StripeOnramp("${Constants.stripeKey}");
initialize();
function initialize() {
const clientSecret = "${ramp.session}";
const onrampSession = stripeOnramp.createSession({
clientSecret,
appearance: {
theme: '${theme.brightness.name}',
},
});
onrampSession
.addEventListener('onramp_session_updated', (e) => {
if (e.payload.session.status === 'fulfillment_processing') {
Bridge.postMessage('close');
}
})
.mount("#onramp-element");
}
});
</script>
</head>
<body>
<div id="onramp-element" />
</body>
</html>
(What we show in the webview)
Hello ๐ can you give me a quick summary of the problem and where things trailed off?
Sure!
We have two problems right now:
-
We have apple pay enabled in the dashboard and stripe crypto docs say it is supported, but our users can't use apple pay. It doesn't show for some people, and for the people it shows for it just infinitely loads when they try to pay.
-
The id verification button is getting cut off. The stripe widget doesn't want to take up the full screen height im giving it or have a scroll for overflow and is cutting off the button to take a picture of their id, effectively blocking them from actually checking out
Do you have a test page where I can see this apple pay behavior?
And unfortunately we don't know much about betas so I don't think I can be all that helpful with the onramp element. If you reach out the beta team with a description of your problem and your code, they should be able to help you (we typically give a beta team email address along with beta onboarding)
We've already tried talking to them and haven't been helpful
Which beta are you talking about?
That functionality is still in beta. https://docs.stripe.com/crypto/integrate-the-onramp
Can we add someone in here who can help?
It is not generally released yet, this server mostly deals with functionality that has been generally released.
I can try to take a look but if I can't find much talking to the beta team really would be the way to go
we're using a webview with this site: https://crypto.link.com/
which isn't in beta
and has been live for almost two years
Can you add someone from the beta team into the chat? We've tried emailing back and forth but hasn't been helpful for a week
Your website is not in beta but the Stripe functionality that you are using is in beta. This server thinks in terms of Stripe functionality. Unfortunately I cannot add members of the beta team to this chat.
I do see that in the previous thread Rubeus asked if you had console output from that webview. Have you tried looking in to that and if so did any error messages show up?
For the apple pay we can check console logs but it seems like something opaque that we can't do anything about because the physical apple pay widget infinitely loads
Im assuming theres something on stripe's end going on there
For the frontend button being cut off there isn't anything to log because its a display element thng
We copied the css from the docs and crypto.link.com
Gotcha, still catching up on this server for a minute but I will test on your site and see if I can find on anything else.
But on the previous step it shows the agree and continue button
It seems the stripe iframe itself is prevent overflow scrolling, not us
Do you have a link to the page that you are webviewing to? Apologies things got busy and I was just getting back to this. Like my colleague I cannot test using TestFlight
The page with the onramp element to be clear, not the link site
Its just html code we inject into a webview it doesnt have a link
I can send the html code?
@alpine shell
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Crypto Onramp</title>
<meta name="description" content="A demo of hosted onramp" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<script src="https://js.stripe.com/v3/"></script>
<script src="https://crypto-js.stripe.com/crypto-onramp-outer.js"></script>
<style>
html, body {
margin: 0;
padding: 0;
height: 2000px !important;
overflow: scroll;
}
div {
min-height: 1000px !important;
}
#onramp-element, iframe {
margin: 0px;
padding: 0px;
aspect-ratio: 2 / 3;
width: 100%;
min-width: 320px;
max-width: 500px;
min-height: 600px !important;
max-height: 2000px;
display: block;
user-select: none;
transform: translate(0px);
}
.โ๏ธ{
height: 2000px !important;
overflow: scroll !important;
}
</style>
<script type="text/javascript">
document.addEventListener("DOMContentLoaded", function() {
const stripeOnramp = StripeOnramp("${Constants.stripeKey}");
initialize();
function initialize() {
const clientSecret = "${ramp.session}";
const onrampSession = stripeOnramp.createSession({
clientSecret,
appearance: {
theme: '${theme.brightness.name}',
},
});
onrampSession
.addEventListener('onramp_session_updated', (e) => {
if (e.payload.session.status === 'fulfillment_processing') {
Bridge.postMessage('close');
}
})
.mount("#onramp-element");
}
});
</script>
</head>
<body>
<div id="onramp-element" />
</body>
</html>```
We ripped this right out of the docs
And have been adding tons of css style to try to make the inner parts of the iframe stop cutting off
Unfortunately I am having trouble adding my own account to the beta. I am sorry to pass you back again but I think continuing your conversation with the Crypto team is the best way to diagnose this. If you have not already, definitely send them that and your app's WKWebview setup code so that they can more closely reproduce what you are doing. If you also let them know the CSS things that you have tried that will give them leads on what this may be
How do we talk to them
Can you help us escalate this
we have had conversation with multiple stripe people
This is extremely time sensitive and blocking for us
We are supposed to launch on the app store and are expecting high volume and stripe is literally cutting off the verification button in its own webview
We might have to switch to a different on ramp provider
My understanding is that when you were added to the beta we should have given you an email to reach out to specifically for beta questions. So to start, do you have that address and did you already reach out through there?
@tacit bloom
We already reached out through there
Sorry, I meant the email you reached out to
Okay I see that conversation. Similar to earlier in this thread, I think there is confusion around what exactly you are using. While crypto.link is involved, the thing you are primarily working with is our onramp sessions API and onramp element, which are part of the crypto onramp beta. If you reiterate that and send your Webview + HTML code, that should help things get routed properly
https://docs.stripe.com/crypto/integrate-the-onramp
If you have the email address from your onboarding email that the beta team said to reach them that, it may also be worth emailing them with that info as that email should go directly to them
@plush plume
Where do we send this?
I'm having trouble find an address. I will see if my colleagues have a better idea, otherwise reiterating that info and sending that code through your existing email thread will be the best step forward.
Gotcha, and we don't list any other @stripe.com addresses within that email?
Ah, it looks like there isn't an email specific to this beta. I would say follow up in the existing thread with that info
Thanks I'll send them the code snippet
and mention that you helped up
us
is there anyone you can add to discord who can help with this from the team
Unfortunately not. The scope of our knowledge and support only covers generally available Stripe functionality.
Is there an exception you can make? Or contacting someone from the team to get one added tohere. The email hasn't been very helpful. have been going back and forth for a week
Unfortunately not. I apologize, I do understand that that is frustrating but email support is how we support our betas. Support should have instructions on forwarding you to the beta team once the topic is clarified.
okay. can you ask one of the poeple on the beta team to check the email? Just sent over all the relevant infomraiotn
Unfortunately I cannot. I can view emails but I can't push on the people working on them