DragonByte Tech
Well-known member
I think the most appropriate action here is to setup a separate payment profile. Having two checkboxes would make the UX worse IMO.
![[DBTech] DragonByte Stripe Checkout](/community/data/resource_icons/9/9414.jpg?1710593613){kind=icon}
[DBTech] DragonByte Stripe Checkout 2.1.1
- Thread starter DragonByte Tech
- Start date
-
- Tags
- stripe stripe checkout
benFF
Well-known member
This only works when products are specifically defined as either single or recurring.
If a product can be dynamically set, then there's no option to choose different payment profiles.
For example, theme house donate, there's just a checkbox, it wouldn't make sense to also click a payment profile here.
If a product can be dynamically set, then there's no option to choose different payment profiles.
For example, theme house donate, there's just a checkbox, it wouldn't make sense to also click a payment profile here.
benFF
Well-known member
Just had my first recurring payment and it failed.
The reason seems to be there is no "request_key" (or any other field) in the "metadata" array passed through to the webhook.
Single payment:
Recurring:
Ah it seems recurring use the callback to invoice.payment_succeeded instead of charge.succeeded which xen gives error "Event data received from Stripe does not contain the expected values."
The reason seems to be there is no "request_key" (or any other field) in the "metadata" array passed through to the webhook.
Single payment:
Recurring:
Ah it seems recurring use the callback to invoice.payment_succeeded instead of charge.succeeded which xen gives error "Event data received from Stripe does not contain the expected values."
DragonByte Tech
Well-known member
You might want to wait for XF 2.3 and use native XF stripe recurring payments then.
DragonByte Tech
Well-known member
My addon doesn’t add any event hook handler. It was not needed in my test against their testing API. I don’t know what 2.2 handles by default.
benFF
Well-known member
Ok I've found the issue - for a subscription, in the
However in my table, all the records (both subscription and normal all start with
Oh and also which webhook events do you listen to? I just use the ones advised by XF, but do I need extra now?
xf_purchase_request table, the provider_metadata records needs to be the subscription ID - which starts sub_.However in my table, all the records (both subscription and normal all start with
cs_live_al) - before I was using your add-on, they all start pi_ - is that a clue?Oh and also which webhook events do you listen to? I just use the ones advised by XF, but do I need extra now?
Last edited:
DragonByte Tech
Well-known member
As I said, this is an extension to the existing Stripe payment profile. It is not a replacement, so I don’t listen to any webhook events.
As for the different subscription IDs, I have no idea. This addon exists only because I needed Stripe Checkout for my own website, and the recurring payment addition is flagged as experimental because I have no need for it at this time.
As mentioned previously, in XF 2.3 the Stripe implementation natively supports subscriptions, and this add-on will only function to allow you to choose what payment processors are enabled.
DragonByte Tech
Well-known member
DragonByte Tech updated [DBTech] DragonByte Stripe Checkout with a new update entry:
2.0.0 Release Candidate 1
Read the rest of this update entry...
2.0.0 Release Candidate 1
Read the rest of this update entry...
DragonByte Tech
Well-known member
DragonByte Tech updated [DBTech] DragonByte Stripe Checkout with a new update entry:
2.0.0
Read the rest of this update entry...
2.0.0
Read the rest of this update entry...
DragonByte Tech
Well-known member
DragonByte Tech updated [DBTech] DragonByte Stripe Checkout with a new update entry:
2.0.1
Read the rest of this update entry...
2.0.1
Read the rest of this update entry...
DragonByte Tech
Well-known member
DragonByte Tech updated [DBTech] DragonByte Stripe Checkout with a new update entry:
2.0.2
Read the rest of this update entry...
2.0.2
Read the rest of this update entry...
DragonByte Tech
Well-known member
No, this addon is only intended to force Stripe Checkout to use certain payment methods rather than relying on Stripe guessing.
DragonByte Tech
Well-known member
DragonByte Tech updated [DBTech] DragonByte Stripe Checkout with a new update entry:
2.1.0
Read the rest of this update entry...
2.1.0
Read the rest of this update entry...
DragonByte Tech
Well-known member
DragonByte Tech updated [DBTech] DragonByte Stripe Checkout with a new update entry:
2.1.1
Read the rest of this update entry...
2.1.1
Read the rest of this update entry...
benFF
Well-known member
I know this is really late now and I see you already removed recurring payments.
But for anyone still on XF 2.2 using 1.2.0 beta of this add on and you want recurring to work, you need to add the following function to the "DBTech/StripeCheckout/XF/Payment/Stripe.php" file:
PHP:
public function setupCallback(\XF\Http\Request $request)
{
$state = parent::setupCallback($request);
if (!$state->getPurchaseRequest() &&
!isset($state->event['metadata']['request_key']) &&
isset($state->event['subscription'])
&& is_string($state->event['subscription'])
&& strpos($state->event['subscription'], 'sub_') === 0
) {
if (strpos($state->event['id'], 'in_') === 0)
{
$lines = $state->event['lines']['data'] ?? [];
foreach ($lines AS $line)
{
$requestKey = $line['metadata']['request_key'] ?? null;
if ($requestKey)
{
$state->requestKey = $requestKey;
break;
}
}
}
}
return $state;
}Similar threads
