#Phillip- BGFS
1 messages · Page 1 of 1 (latest)
hello! are you using a third party with Stripe or implementing Apple Pay with Stripe yourself?
if you're implementing Stripe with a third party, you would want to reach out to the third party for help. They'll be able to better advise you on troubleshooting steps.
you'll need to reach out to the plugin for help. unfortunately, we don't have any insights on how the third party implements / integrates with Stripe
okay
thanks
yea same issue
@forest sleet
here the last guy said just do step 2
and we have
and we are still having issues
and its a stripe issue it seems
to clarify, what was mentioned before was that
2/ your WP platform needs to then register the exact same domain that you had above but as described here: https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-using-with-connect
(that second code snippet to register the domain by the Platform on your account is the key step they need to do in live mode)
I just took a look, the domain still isn't registered correctly. You MUST register the domain using the platform's secret key and using the Stripe-Account header as per that link / section
Yes we have registered same domain in stripe
https://blackgirlfilmschool.com/
@sleek totem can you check and verify?
just checked, it's still incorrect. What's the code snippet that you're using to register the domain? Omit the secret key when you share it here
For context, we have internal tools to check if the domain is being registered by the platform on the connected account. That information doesn't show on your Dashboard
but how it's incorrect? domain is same
@sleek totem so what i have to do now? because domain is already added in stripe
delete the existing domain, then redo it according to the instructions in that documentation shared previously. It'd probably be good if you can share the code snippet (omit the secret key) that you're using to register the domain so that i can take a look at see if it's correct
please don't share your secret keys on a public channel
you just shared a screenshot of all your API keys, at this point, it's considered compromised and I would strongly recommend you roll all of them
redact the secret key
@forest sleet are you a developer from the plugin which @sterile garden is using?
Yes
then can you share the code snippet which you're using to register the Apple Pay domain?
then this wouldn't work then
registering the domain requires the secret key of WPgive
we have that
it's not something which a platform would and should share though
are you sure you didn't mistake that for your own secret key?
Yes
@forest sleet share but remove the secret key
@sleek totem where do we add the code snippet?
in WP giving
this is a one time registration, you don't need to add it anywhere in WPGiving. You can run it using cURL also if that's more convenient :
curl https://api.stripe.com/v1/apple_pay/domains \
-u {PLATFORM_SECRET_KEY}: \
-H Stripe-Account:acct_1HWx2HDi58iphYyX \
-d domain_name="blackgirlfilmschool.com"
@forest sleet you see this?
but we have added domain using plugin
there is stripe adon they connected our domain
so why we need to use curl?
you can't do this registration via the Stripe Dashboard if that's what you're asking.
Can you give us steps to register
you need to do it using the API, using cURL is just one example of registering via the API
I do think that this is something which should be done by WPGive as part of their plugin, which is why i'm a bit confused as to why you're handling it from your end.
it seems like its registered. @forest sleet can you confirm
You can see this is givewp documentation and i have followed same
there is not mentioned to add curl
even i have entered licence key in givewp plugin
i understand that you're following their guide. But from our perspective, their code isn't registering the domain correctly.
so it's a bit of a complicated situation here, their code isn't registering the domain correctly from our perspective, and you as the plugin user have no way of registering the domain correctly either - i really don't think that the secret key you have belongs to WPGive.
The secret key is something which should be kept securely and should never be passed to someone else to use at will. A secret key has full administrative rights on their Stripe account.
if you can, maybe request a developer from GiveWP plugin to reach out to us, it may be easier for us to resolve this issue then
we do not have access to a GiveWP developer. The issue is Stripe since the screen shor @forest sleet shared showed that the plug in is registered to my Stripe Account ID
GiveWP is the one that implements the integration i.e. how Apple Pay is offered to your customers as a payment method
and that integration / implementation right now is incorrect
can you maybe share the link to your site where Apple Pay is supposed to be displayed?
let me take another look
it looks like it's https://blackgirlfilmschool.com/support-bgfs/
and yeah, unfortunately, however it is that the WPGive plugin is registering the domain, it's definitely incorrect
it's using your secret key to register the domain. But what needs to be done is to use WPGive's platform's secret key and the Stripe-Account header to register the domain on your account
I'm sorry and I wish I could help more, but there doesn't seem to be much else that can be done without WPGive being involved at this point.
there is no such thing as the WPgives's Platform secret key
you wouldn't be able to see it or access it from your end
But every Stripe account has a secret key, and WPGive (as a platform on Stripe) would have their own secret key as well
but they are a stripe apprived partner
which is why we selceted them
we are connected to stripe already
so i think we are pass the step you are trying
As you told that domain is not registered then why here it's showing conencted
that isn't a Stripe Dashboard, it looks like a WPGive Dashboard. I don't have any context as to what connected indicates
can you share the stripe version
can you share what you are seeing
where will the connection be? Wordpress?
sorry, i don't quite understand the question?
My first question is can you share where you see that the domain is not registered?
second, where will I be able to see the if the domain is registered?
no, unfortunately not. That's an internal tool and isn't something which I can share. You won't be able to view who registered the domain, all you can see is if that particular domain is registered.
The domain is registered by your Stripe Account - this isn't correct. The domain needs to be registered by WPGive using their secret key and the Stripe-Account header.
The domain is registered, but it's registered by your Stripe account - this is wrong. It needs to be registered by WPGive.
This discussion that we're having now isn't very productive. You really need to involve WPGive in this discussion
do they not have a support email for you to reach out?
we have and they said its a skype issue
Stripe
the point us to hte fact that the site is registered on their side
and share that screen
and that is the same thing you are saying
that it should not be registered with stripe
ther @sleek totem
can we add anyone that can contribute to a fix?
Hey 👋 gimme sometime to catch up
Yes I am reading the old thread and this thread
Okie I have got the situation. It's correct that there is a missing piece and only GiveWP (developer/support) people can help with. They probably provide the option in somewhere on their dashboard that maybe you haven't recognized, or they have a bug on their own.
One quick question, I found this on their forum: https://wordpress.org/support/topic/apple-pay-is-not-appearing/ Have you enabled the setting mentioned here?
Donations > Settings > Payment Gateways > Stripe > Apple/Google Pay
Private browser doesn't matter, as my colleague said
I know you assume it should work if it shows in private browser, but actually it's not. In private browser the button always display, but in normal browser it won't. We know it as a fact
sure
but i still dont think i understand why your partner plug-in is not working
works for this site
https://wordpress.org/support/topic/apple-pay-is-not-appearing/ Have you enabled the setting mentioned here?
I checked this and there is no any issue
I have enabled option for google pay and apple pay
Is that your site? Yes it doesn't have issue.
I think your site is https://blackgirlfilmschool.com
Yep, so you have enabled the options in GiveWP dashboard?
Did you just enabled it or way before?
before
can you check you system that sees if the domain is registered?
you colleague mentioned it
yes it is registered but doesn't look like correctly. We have said the registering step should be done by GiveWP
but thats done
@forest sleet did you setup your site in Test mode or Live mode? and where?
thats why we are confused
Live
Why confused? It's a step needs to be done by GiveWP and our understanding is that you can't register on your own
@forest sleet by setting a live key to GiveWP?
Yes i have added my domain in givewp and updated licence in givewp plugin
Have you ever succeed in completing a Payment and see it in Stripe Dashboard before? Even non-ApplePay
yes
Can you share an example Payment Intent Id? pi_xxx
yes, that was a private server
@lucid abyss it's stripe issue not givewp plugins
I am still checking something
We are talking with some other from my team
okay
we are still looking for help on this
hi! looks to me like the issue here is that you configure the plugin is wrong, or the way the plugin is implemented is wrong. For some reason you are using the publishable key of your account(which is fine), but you/the plugin are also initialising our library with the Stripe account ID of your account, which is not needed.
I'd suggest working with the support of the plugin you use. One thing you can try to do is look at how you configure the plugin and if there's any setting or input where you had to supply your account ID (acct_1HWx2HDi58iphYyX), then remove that.
alternatively, is that plugin wants to do Connect payments, then you need to fix the registration
which means you would need to go the dashboard of your Stripe account, delete the registration there, and work with the plugin to have them register the domain for you.
I'm not sure which is the correct option, since it depends on the plugin and what way it wants to process the payments. You 100% need to talk to them, they built this and would know how Stripe Connect and Apple Pay works.
I have connected using API keys
I also see the plugin is using the wrong API key, it uses the API key of your connected account, and not the API key of the platform account GiveWp.
and it's connected with stripe
I don't know what that means sorry
yes, the wrong API key. The way Apple Pay Connect usually works is the platform uses their API key from their own Stripe account, and they pass the ID of your connected Stripe merchant account. Here for some reason your page is using the API key of your connected Stripe merchant account and not GiveWP's key.
so either
i) the plugin is misconfigured by you
ii) the plugin has an issue
iii) the plugin doesn't intend to use Connect
these are 1ll 100% things we can't help you with at all and you need to work with them on.
if it's wrong then why it's working on private browser?
because Apple Pay always works in a private browser
apple pay is showing in private widnow
can you tell me one thing
my plugin is connected with stripe or not?
yes because in private windows Safari doesn't check if the domain is registered, since knowing if a page can support Apple Pay gives signal and helps fingerprint the browser, so they just make it always work to protect privacy that way
I have no idea what that could mean unfortuantely
yep but it 100% depends on the plugin and how it intends to work, there's multiple ways of doing this
in some ways, they need you to copy paste your API keys to them; in other ways, they wouldn't need that at all
okay
so again it really depends on the plugin you use and how it's configured. We really can't help you here, this Discord and our direct support is for developers building direct integrations with our APIs and libraries. You need to work with the support of the plugins/platforms you're using.