Showing ideas with label payments.
Show all ideas
Allow a customer-level setting that enables/hides payment methods. For example, I have a small number of customers who cannot be removed from their price group, but who I want to force into Proforma Invoicing rather than Creditcard. By linking the payment method to the price group, I have to double up the number of price groups, one for normal people and one for those with bad credit etc.
... View more
See more ideas labeled with:
-
checkout
-
payments
Our payment partner - Adyen offers a feature to see which browser a customer used to make a purchase, so long as the order was made using their Card services. For other standalone payment methods such as Amazon Pay and PayPal; I would like to suggest an information box within the order history for the admins benefit only, so that we may track which Browser a person used to complete an order and monitor whether a certain browser and/or version is causing errors or failing to track conversions within Bing or Google. The idea came from the information found in our Adyen control panel.
... View more
Currently PWA Studio supports Braintree payments out of the box in its Venia storefront implementation. It will be great if it can support all the payment methods which comes by default with luma theme. Here I am requesting to have Purchase order payment method compatible with PWA studio in native magento. Thank you!
... View more
As part of the new 3-D Secure standard that is coming into force in Europe, there are a number of new parameters that should be sent to credit card acquirers. For a full list of the new fields check Credit Card 3DS2 Fields Currently missing information as far as my research showed: customer last login date customer password change date how many attempts to add a credit card to vault (e.g. tried to add 100 credentials and only the last one was valid) customer suspicious activity (there should be a way for a merchant to mark a customer as suspicious) street 3 field for billing and shipping address mobile phone and work phone (add 2 additional phone fields) expected delivery date for preordered products To ensure full compliance with the 3-D Secure standard this fields should be added.
... View more
See more ideas labeled with:
-
checkout
-
payments
Please allow "Purchase on Account" to be an available payment method when placing orders in the Admin on behalf of a customer who does not want to enter an order online. I'm shocked that Magento does not allow orders to be placed against a company's credit limit while placing orders through the Admin. Many B2B customers will simply want to send in a PO rather than ordering through our frontend, but lacking this feature we have no way to accept that PO and account for it on the company's credit limit. What's the use of this credit limit otherwise???
... View more
See more ideas labeled with:
-
admin panel
-
payments
Firebase Push Notification module: This module is very frequently used with mobile applications. We can provide features listed below: Admin area to configure firebase authentication key. Rest API to save device token when someone gets logged-in with mobile application. Send push notification to mobile devices on various events like new order, order status change, abandoned cart etc. Send bulk notifications for newsletters and marketing campaigns. Save the list of notifications sent to customers and allow resend the notifications. I have already prepared a sample module and planing to publish it on Magento Marketplace.
... View more
See more ideas labeled with:
It is frequently the case that, in a B2B scenario, there is a significant amount of divergence between pricing groups and customers who are / aren't taxable. For example, a supplier who has wholesale customers, some of which are non-profits, may want to put many companies in a single pricing band but then only charge tax to the for-profit companies. Because Magento currently overlaps these concepts completely (customer groups are how you define customer tax class) it is impossible to manage the concept of prices separate from the concept of taxability. This can be worked around by creating a taxable and non-taxable version of each price tier but this is conceptually duplication for the purpose of pricing and can become challenging to manage. Also, depending on the number of price tiers, this can take a scenario that fits into a manageable number of customer groups and cause it to explode (double?) into MANY groups. 25 price tiers isn't so bad. 50 tiers (taxable / non-taxable versions) is a LOT more painful, including from a UI perspective in the admin. Ideally, in my opinion, a customer's taxability status would be something that is set on the customer account independent of their customer group. This is conceptually proper and prevents the pricing group duplication issue. Also, though I'm not the best developer, this seems like a sane way to handle things to me because taxability seems to not need the same level of indexing that pricing does. It's a "figure in real time in the cart" value and therefore (I would think) could just be looked up on the customer record when needed. Thoughts / feedback appreciated but it would be nice to see Magento go this direction, especially with focus on B2B. ++version would be support for taxability as a discrete option on a company record that populates down to children accounts if/when company/child account become a thing
... View more
See more ideas labeled with:
-
payments
Full details can found in https://github.com/magento/magento2/issues/19858 Initial GitHub Issues #19858 was reopened on Jul 30, 2019 with argumentation: I'm reopening this issue for two reasons: First this behaviour was working in M1. When a catalog price rule changed the product price in M1 this was reflected in the discount fields of the sales_order_item database table. This way you could always determine if a discount was used when the product was ordered. Secondly, either way, a special price or a price different then the original price is a discount, and it shouldn't matter where this discount is applied. It could be applied in the catalog or it could be applied in the cart, you're giving a discount on the price of the product. This should be registered as a discount. Please reopen the internal tickets within Magento Jira as well. Based on multiple feedbacks in slack and comments on the issue, it seems still a pain point for the community The issue was re-verified on the latest 2.3-develop branch and Confirmed again 1. Magento 2.3.*. 2. Catalog price rule which is enabled. 3. A visible and enabled product. Steps to reproduce 1. Create a product with the sku 'A'. 2. Create a catalog price rule for the product with the sku 'A' with a percentage discount or a fixed discount. 3. Apply and save the catalog price rule. 4. Run the command `bin/magento index:reindex`. 5. Place the product with the sku 'A' in your cart. 6. Complete the checkout process. Expected result 1. Product 'A' is shown with the discounted price on the product detail page and in the checkout [frontend]. 2. In the backoffice the discounted amount/percentage is shown in the order per order item [backend]. 3. In the table `sales_order_item` the `discount_amount` or `discount_percent` value is saved [database]. Actual result 1. Product 'A' is shown with the discounted price on the product detail page and in the checkout [frontend]. 2. In the backoffice the discounted amount/percentage is *NOT* shown in the order at all [backend]. 3. In the table `sales_order_item` the `discount_amount` or `discount_percent` value is *NOT* saved [database]. At the moment there is no proper way to ascertain whether an order item actually has a discount or not. The `applied_rule_ids` does not necessarily mean it is a discount for the product, it could also be free shipping for example.
... View more
See more ideas labeled with:
-
admin panel
-
checkout
-
other
-
payments
Using the Order API in either SOAP or REST mode with XML returns the payment's `additional_information` in an unidentified list, an array of strings without keys: <additionalInformation>
<item>0</item>
<item/>
<item/>
<item>Credit Card</item>
<item>1</item>
... These values are fairly useless and should be identified with something like this: <additionalInformation>
<save>0</save>
<acceptjs_key/>
<acceptjs_value/>
<method_title>Credit Card</method_title>
<response_code>1</response_code>
... The keys are being stripped by the Magento\Framework\Reflection\DataObjectProcessor, though I don't think that is the real cause as I was not able to change the way this data is sent.
... View more
See more ideas labeled with:
-
API
-
payments
On the ORDER > INVOICE > CREDIT MEMO form, the field Grand total is not updated when you change any value in the Refund totals block. We should be able to see and confirm the $ amount to be refunded to a Customer before submitting a refund to a credit card (or to any form of payment).
... View more
See more ideas labeled with:
-
admin panel
-
CMS
-
payments
If your locale is not set to en_US, the PayPal module uses the really old button style: It would be better for an admin to be able to choose the PayPal button flavour inside the payment method, and have the following choices: https://developer.paypal.com/docs/classic/api/buttons/ Also, see Magento\Paypal\Model\Config line 983 (Magento 2.1.3)
... View more
See more ideas labeled with:
-
payments
We are a canadian business, and the exchange rate has been getting worse and worse. Displaying prices in CAD on our website gives an impression of expensiveness. I'd like to replicate what eBay/Paypal does: customer can choose to pay in USD or CAD. If they pay in USD, their credit card will do the conversion (unless they have a USD credit card). If they pay in CAD, they will pay the price displayed on the website. If they pay in USD, I'd like the money to be deposited in our USD account. If they pay in CAD, I'd like the money to be deposited in our CAD account. It seems like what I'm seeking is not supported by Adobe Commerce / Magento 2, and yet: I think it would be a fantastic improvement.
... View more
See more ideas labeled with:
-
checkout
-
extensions
-
payments
This would provide ability to set certain products to be only purchasable using the allowed payment methods. For example, this would exclude product from global payment methods to be purchasable only by credit card.
... View more
See more ideas labeled with:
-
payments
Request: When defining Tax Classes, allow Tax Calculation Based On to be configured on a per scope basis. Use Case: Referred to as Nexus, a store with resellers or Shipping Origins located in different states, and shipping to states separate from where the reseller is located, will need to charge state tax for a subset of states that varies between each Shipping Origin. References for Nexus: https://www.salestaxinstitute.com/sales_tax_faqs/what_is_nexus https://www.taxjar.com/sales-tax/origin-based-and-destination-based-sales-tax Why: Some states charge a destination-based Sales Tax, meaning different resellers , will each need to charge state tax for a varying subset of states. As Tax Classes are Global, this requires custom or 3rd party integration.
... View more
See more ideas labeled with:
-
admin panel
-
payments
-
Shipping
Dear team, At the moment without a required configuration, a single use coupon can be applied many times. Simple check to see if there is missing config: There's no "sales.rule.update.coupon.usage" consumer listed in the app/etc/env.php file. $ grep -i usage app/etc/env.php $ To fix this issue, the steps from this doc has to be implemented: https://devdocs.magento.com/guides/v2.4/config-guide/mq/manage-message-queues.html Instead of having this issue which affects many users, can this bug be fixed by adding the setup (fix) as default as a patch or added to future releases of Adobe Commerce?
... View more
Version: Magento 2.4.2 Payments: Opayo PI integration Issue: Orders with a failed payment create "Pending Payment" state order and subsequently empty customer cart and don't allow for a payment re-attempt. This occurs for any payment/card failure (wrong digit, failed 3d secure, wrong CVC) These are very common user errors for ecommerce. This creates negative user experience as the customer then has to re-shop for their cart content and re-checkout. This is because: 1. Magento default is for orders to be placed into order state "Pending Payment" as the checkout page is redirected for payment validation from bank/provider (3d Secure). This 'creates' the order whilst payment is sent for approved/refused. As 3d secure is worldwide mandatory in 2022 this will impact all store checkouts. 2. If this fails due to incorrect card details or fail of 3d secure, the order remains Pending Payment and the customer has their basket subsequently cleared Suggestion: Orders should not be created until payment is authorised from provider. If refused, return to checkout page. If authorised, proceed to order creation upon success. Allow for cart data to be retained and re-provided if payment is failed, not to create Pending Payment order. This causes many issues for sellers and is a huge cause of abandoned carts and negative feedback. This should be native behaviour for Magento to provide customers another attempt to pay rather than removing the cart and placing useless Payment Pending order.
... View more
We want to be able to review which admins gave store credit at the end of the day in an easy, organized manner. Can we put in a feature request, so that under: system -> action logs -> reports [-> store credit] we would like to be able to produce a report that shows who added, subtracted, or spent store credit from the admin panel. it should be an option in these logs to see what admin takes the action of adding, removing, or changing store credit amount.
... View more
See more ideas labeled with:
Magento's current behavior when creating partial invoices, is to bill the entire shipping amount of the order on the first invoice, regardless of how many items have been invoiced. This is problematic when products ship at different times, which can happen frequently if a store drop ships often. Here is an egregious example: A customer purchases two products, a Widget that has Free Shipping, and a Gadget that costs $100 to ship. 2. The Widget ships first, so we must invoice the Widget. 3. When we go to invoice the Widget, we do not want to invoice any shipping, because it was eligible for Free Shipping. However, Magento does not allow us to specify how much of the shipping should be included on the invoice, so the invoice includes the shipping amount for the entire order. 4. When the Gadget ships, we go to invoice it. There is no shipping charged on that invoice, because it was all charged on the first invoice for the Widget. 5. Customer and Accounting frustration ensues. The ability to specify a partial shipping amount on an invoice, up to the total amount charged at the time of order, would solve this issue.
... View more
See more ideas labeled with:
-
admin panel
-
payments
-
Shipping
Issue: When applying a gift certificate to an order, Magento doesn't currently see that as a payment on the order. It's applied as more of a discount as far as order totals are concerned. Since most OMS / ERP applications look at gift certificates as a payment instrument this can cause unneeded customization. See the attached screenshot for more information. Solution: Apply the gift certificate as a payment instrument and list it as a part of the Total Paid on an order. Example
... View more
See more ideas labeled with:
-
payments
We are using tier pricing to accurately present a price for a product. The situation is that if we have an item where we are selling e.g. 500 @ £23.68 - the individual cost per item is £0.04736 Magento only appears to calculate 2 decimal places making the item £0.048 This would make our item £24.00 In this case, as with all others, the price is wrong!
... View more