MultivendorX Pro
-
Posts
-
-
After changing from Stripe Standard to Stripe Express, we are getting an error at checkout. “ERROR CREATING CHARGE RECORD WITH STRIPE: TO CREATE A DESTINATION CHARGE ON A CONNECTED ACCOUNT WITH
TRANSFERSCopyBUT WITHOUT THE
CARD_PAYMENTSCopyCAPABILITY ENABLED, USE TRANSFER_DATA[DESTINATION].” There was no issue connecting a vendor with a new Express account but when I try to checkout with that vendor’s products, this error occurs every time. I have already provided access to the dev site for other Stripe payout issue in my last ticket in case you need to login to the site. Thank you.
-
-
-
-
-
-
-
-
Hi Moumita, it looks like with the way MultivendorX is coded, it requires the Payments option to be enabled for Connected accounts even though in Express it shouldn’t be necessary and by default, this is not enabled so anyone wanting to use Express accounts would have to go into their Stripe Connect settings and turn this on for Connected accounts. Here is the screenshot of what the setting looks like under Stripe Connect settings: https://prnt.sc/RCYnaoCz1y0T. As you can see ‘Transfers’ is by default turned on and required but ‘Payments’ is not. I had to turn it on.
Now I’ve got that working, but the statement descriptor is still showing as the vendor instead of the marketplace. I’m addressing that with Stripe next.
-
-
Moumita, I contacted Stripe about this. I was trying to set the statement descriptor that shows up on the customer’s credit card statement with the name of the marketplace. I thought we could do that either in Stripe account settings or in the API request, but it seems like that’s not entirely possible. I added a statement descriptor via a hook but it doesn’t actually replace the default statement descriptor but acts as a suffix. Here is the code snippet:
add_filter( ‘stripe_marketplace_create_stripe_destination_charges’, ‘stripe_update_statement_descriptor’ );
function stripe_update_statement_descriptor( $charge_data ) {
$charge_data[‘statement_descriptor’] = ‘XXXXXXXX’;
return $charge_data;
}That ends up changing the statement descriptor that the customer sees on the credit card bill from something like “XYZ” to “XYZ*XXXXX” so it just adds * and then the dynamically set statement_descriptor as a suffix.
I’m not sure if that helps or makes any sense, but Stripe basically told me that was expected behavior and there was no way to do what I wanted with replacing the entire statement descriptor.
-
-
-
The topic ‘Stripe Express Error at Checkout’ is closed to new replies.