Skip to content

Adobe Payment Services

Link to original module

Hyvä Module Name

Magento versions

  • Magento Open Source 2.4.4 or newer
  • Adobe Commerce 2.4.4 or newer

Module Versions (if applicable)

  • 2.6.0 or newer (TBC)

Features to be implemented

All points are rated according to priority as P1 (critical), P2 (important), P3 (minor).

  • basic - does not break layout/design

Note: this issue is for features related to the theme only. checkout-integration-tracker#546 for details on Hyvä Checkout compatibility.

Minicart (global)

The below assumes 1 or more items are in the cart and applicable methods are enabled in config. Methods display underneath the proceed to checkout button.

image

External Payment Wallets:

  • [P1] Apple Pay
    • Safari only
  • [P1] Google Pay

PayPal Smart Buttons:

  • [P1] PayPal
  • [P2] PayPal Pay Later
  • [P2] Pay Later interest payments message
    • Varies based on cart total (e.g. 'pay in 3 interest free installments of X' if threshold met, or 'from X-Y' if not)
  • [P2] Venmo
    • US only

Product Detail Page (/catalog/product/view/id/{id}/)

The below assumes the current product is in stock and applicable methods are enabled in config. Methods display underneath the add to cart button.

image

External Payment Wallets:

  • [P1] Apple Pay
    • Safari only
  • [P1] Google Pay

PayPal Smart Buttons:

  • [P1] PayPal
  • [P2] PayPal Pay Later
  • [P2] Pay Later interest payments message
    • Varies based on product price (e.g. 'pay in 3 interest free installments of X' if threshold met, or 'from X-Y' if not)
  • [P2] Venmo
    • US only

Product validation:

  • Ensure required options are selected before triggering selected payment option
    • Show standard validation error message to customer where not
  • Ensure qty selected is available before triggering selected payment option
    • Show standard validation error message to customer where not

Cart Page (/checkout/cart)

The below assumes 1 or more items are in the cart and applicable methods are enabled in config. Methods display underneath the proceed to checkout button.

image

External Payment Wallets:

  • [P1] Apple Pay
    • Safari only
  • [P1] Google Pay

PayPal Smart Buttons:

  • [P1] PayPal
  • [P2] PayPal Pay Later
  • [P2] Pay Later interest payments message
    • Varies based on cart total (e.g. 'pay in 3 interest free installments of X' if threshold met, or 'from X-Y' if not)
  • [P2] Venmo
    • US only

Order Review Page (/paymentservicespaypal/smartbuttons/review/)

Screenshot_2024-06-06_at_08.14.38

  • [P2] Isolated/simplified header and footer
    • Header: logo and page title only
    • Footer: Copyright notice only
  • [P1] Select shipping method and update totals
    • Done via XHR in Luma
  • [P1] Display selected shipping address (not editable)
  • [P1] Display payment method (not editable)
  • [P2] Allow adding/removing a coupon code
    • Note: this does not appear to work in Luma. Success/error messages are shown based on coupon validity, but totals are never updated when successful and coupon field remains in it's default state
  • [P3] Toggle coupon code section (hidden by default)
  • [P1] Shopping cart items list
    • Image
    • Name
    • Price
    • Qty
    • Subtotal
  • [P2] Edit Shopping Cart link
    • Directs to /paymentservicespaypal/smartbuttons/cancel/ to cancel/end current review process
  • [P1] Totals
    • Subtotal
    • Shipping (when selected)
    • Tax
    • Grand total
    • Note: it is assumed discount and any other totals, e.g. gift cards in Enterprise, should also display here, but discount not working at present in Luma
  • [P1] Place Order button - only enabled if shipping method selected
    • Directs to /paymentservicespaypal/smartbuttons/placeorder/ and then redirects user to /paymentservicespaypal/smartbuttons/success/ on success

Order Success Page (/paymentservicespaypal/smartbuttons/success/)

This route appears to have identical output as the layout XML instructions only include an update handle to the default checkout_onepage_success handle, i.e. all customisation appears to be backend only so no compatibility effort should be required.

  • [P1] Success page renders as per default

Account Area - Stored Payment Methods (/vault/cards/listaction/)

The below assumes a customer account and a card has been saved as a stored payment method at checkout during a previous when logged in.

Screenshot_2024-06-06_at_10.55.11

  • [P2] Stored cards for Payment Services appear within the vault
  • [P2] Stored cards for Payment Services can be removed from the vault

Additional Testing Checklist

All config settings should be tested to ensure they honour the current website/store scope

  • [P1] Payment services code only runs/outputs on the frontend when enabled in config
  • [P1] Methods/buttons only display in the relevant locations when enabled / visible in config
  • [P1] Method action (e.g. authorize) matches values set in config
    • Valuess match but implementation only supports authorize - throwing errors for authorize and capture
  • [P2] Method titles match values set in config
  • [P2] Method sort order matches values set in config
  • [P2] Button styles match values set in config
  • [P2] Ensure debug mode works when enabled in config

Contributors

  • Bemeir

Voting

Use 👍 to cast your vote.

Edited by Jenul PhoneLcdParts
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information