Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
This task is part of the meta issue for supporting onsite gateways/stored payments methods (See #3162190: [META] Support onsite payment gateways / stored payment methods).
We currently don't return the available payment options which means the frontend isn't aware of the payment methods available for paying an order.
We should probably first focus on returning the available reusable stored payment methods, and worry about returning the available "new" payment options in a followup since we're currently focusing on supporting payments via stored payment methods.
Comment | File | Size | Author |
---|---|---|---|
#4 | interdiff_2-3.txt | 1.14 KB | jsacksick |
#3 | 3162349-3.patch | 11.74 KB | jsacksick |
|
Comments
Comment #2
jsacksick CreditAttribution: jsacksick at Centarro commented@mglaman: I still think it's good to "split" the work into small chunks (to make it easier for commits). Nothing is preventing us to make changes once it's committed assuming we don't tag a release.
I think it's fine to just return the payment options as is...
Comment #3
jsacksick CreditAttribution: jsacksick at Centarro commentedComment #4
jsacksick CreditAttribution: jsacksick at Centarro commentedComment #5
jsacksick CreditAttribution: jsacksick at Centarro commentedThe bump to Commerce 2.x dev is required because of #3163464: Add a PaymentOption::toArray() method.
Comment #7
jsacksick CreditAttribution: jsacksick at Centarro commentedCommitted, there's a possibility the payment option "id" will be removed before the release though...
Comment #8
jsacksick CreditAttribution: jsacksick at Centarro commentedAttaching a sample "payload":
Comment #10
mglaman