💳 Apple & Google Pay - New Plugin from Zeroqode

@ZeroqodeSupport

:white_check_mark: Update

I found and fixed the first issue that was causing the plugin not to render.
The problem was that the country field was being passed as empty — setting a default value resolved the rendering error successfully. :+1:


:lady_beetle: New Bug: “Missing required param: shipping[name]”

When I checkout for orders without shipping details, i able to complete checkout successfully.
However, when I try to checkout for orders that require shipping details, I get this error:

Missing required param: shipping[name].

Even though I’ve already filled “shipping” in the plugin element’s Delivery title field, the error still occurs.
I also tested this on a new clean test page, but the same issue persists.


:speech_balloon: Additional Questions

Why are the User email and name not being passed to the backend API (used for payment intent creation)? from apple/Google pay.

  • The plugin does return the user’s name and email on the frontend when the payment success/fail event is triggered,

  • But these values are not included in the data sent to the backend, which I need to check if the customer already exists.

Would you please confirm:

  1. If shipping[name] needs to be explicitly included as a separate parameter in the backend call?

  2. And how can we access the user’s name and email from Apple Pay directly in the backend for creating or checking the customer record?


Thanks a lot for your help! :folded_hands:
Any guidance or examples on handling shipping[name] and passing user data to the backend would be really appreciated.

:gear: Plugin Settings & Backend Configuration

Below are the relevant screenshots:
:camera_with_flash: [Plugin settings image]
:camera_with_flash: [Backend API workflow configuration image]

(These show how I’m getting the workflow params and defaulting to the current user.)

backend:

Hi @Bakhtomer ,

Thanks for getting back to us and providing the detailed information! :folded_hands:

Regarding your questions:

The shipping[name] parameter actually corresponds to the customer name. If this field is empty, the response will throw the error you’re seeing. We highly recommend checking how this is configured on our side for reference: Apple & Google Pay Backend Setup Demo.

For checking if the customer already exists, it’s best to use the customer ID pulled in the backend workflow rather than relying on name/email fields. This approach ensures you’re referencing the correct existing customer reliably.

Hope this helps clarify things!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

Hi everyone,

We have successfully published version 1.46.0 of the Apple Pay & Google Pay plugin.

Version 1.46.0 Release Notes

  • Added Stripe Connect support to both elements and all server actions, including Connected Account ID, Charge type (destination and direct), and Order ID. We also added Application Fee and On behalf of seller fields to the actions.

  • Added a new Register Payment Method Domain action for registering domains on seller accounts.

  • Added new custom states (Error message, Payment status, Connected Account ID, Subscription status) and new return values (Payment Intent ID, Subscription status, Payment client secret, and error message in Create a customer).

  • Implemented 3D Secure confirmation for the initial subscription payment and fixed the 3D Secure sequence in one-time payments.

  • Fixed several issues, including the Payment Failed error during server errors, payment window freezing, duplicate buttons, permanent hiding of the element, an extra product in Create Subscription, and the Retrieve Price crash on one-time prices.

  • Added input data validation with clear error text for the amount, acct_ format, fee, and recipient.

For more details on how to configure and use these new features, please review the official plugin documentation at: Apple Pay & Google Pay

If you encounter any issues or have questions regarding this update, please let us know here on the Bubble Forum or reach out to support@zeroqode.com.

Best regards,
Browse all Zeroqode Plugins for Bubble
Banner_Last3

Thanks for the update. Does 1.46.0 change anything for the earlier shipping[name] error or for passing payer name/email to the backend? The release notes mention validation and 3D Secure, but not how shipping[name] is populated or how to retrieve payer name/email in a backend workflow. If not, is the recommended path still to create/find the customer first and pass the customer ID?

Hi @ariettadoggett249,

Thank you for reaching out and checking on the details of version 1.46.0.

Here is how this update handles those behaviors for Apple Pay and Google Pay:

  • shipping[name] handling: Version 1.46.0 does not automatically populate shipping[name]. Instead, it now returns a clear validation error if a shipping address is provided while the Recipient field is empty.

  • Payer name and email: This version does not pass the payer’s name or email to the backend.

  • Recommended workflow: Yes, the recommended approach remains the same. Create or find the customer in advance and pass their Customer ID into the Create PaymentIntent action. You can then look up the customer in your backend workflow using the order_id.

Please let me know if you have any further questions about this setup.

Best regards,
Browse all Zeroqode Plugins for Bubble
Banner_Last3