10413-The totals of the cart item amounts do not match order amounts - paypal

From the magento admin whenever I try to make the payment with zero subtotal and shipping charges  then it shows this error:
Field format error: 10413-The totals of the cart item amounts do not match order amounts
I need the solution to fix this.

PayPal does not process payments for zero amounts. You need to activate a zero amount payment method if you wish to be able to process such "transactions".
If the total amount is not zero, then the error indicates the various subamounts and amounts of items specified do not add up to the total correctly, which PayPal also cannot process.

Related

NetSuite Merge Customers - What Does This Error Mean?

I'm trying to merge two customers and getting the error:
The merge of the entity <merging customer name> was blocked for the following reasons: The selected customers have different pricing levels for the same item. Change the price levels to match.
Where do I find these pricing levels? I've no idea where to even look.
Since the error mentions items, I suspect that the two customers have item-level pricing and there's a mismatch between the two. On the Standard Customer Form (on your custom form it may be somewhere else), go to the Financial -> Item Pricing sublist and cross check the item pricing for each customer. One of them has an item where the Pricing Level column is different between the two customers.

Suppress groups when page count exceeds 1

I have an invoice that is sent annually to thousands of owners. Transactions are grouped by contract and then again by Owner#, meaning there can be multiple contracts for one Owner#. There is a PageNofM in the footer that resets on the change of Owner# grouping.
Our mailing company will only accept invoices that are the same for each recipient. So we remove all the multi-page invoices manually. I would like to output the single page invoices first and then the multi-page invoices.
I have been racking my brain trying to get this to work. I have tried suppressing based on totalpagecount>1 and Googled it in as many different ways I can come up with. So now I'm coming to the experts with my first post. Any thoughts?

How to handle reversal which generated 3 IPNs

Recently a customer filed a bank-reversal to a purchase. The purchase was 100 dollars. However the reversal triggered three IPN requests:
Day 1:
IPN 1:
mc_gross=-96.80
mc_fee=-3.20
payment_status=Reversed
reason_code=buyer_complaint
Day 2:
IPN 2:
reason_code=unauthorized_spoof
payment_status=Reversed
mc_fee=-3.20
mc_gross=-100.00
IPN 3:
reason_code=buyer_complaint
payment_status=Canceled_Reversal
mc_fee=3.20
mc_gross=96.80
For all three IPNs, the txn_type is nil.
Why would one reversal generate thee IPNs? Which one should be used to do clean up on my end? Would there always be three of them?
I think using mc_gross to find the IPN which matches with original amount is not a good idea, because sometimes there are currency conversion losses.

Websphere Commerce Maximum Order Quantity Per Order Change to All Order history and pending

I have here a Websphere commerce 7 Fp 5 Aurora B2B which is using Orgs, contracts and price lists maximum order quantity that we limit each "Store" Org to buy 3 each so that there is enough to go around. We have 3 sets of entitlements to that most guys Max is 3, better stores max is 5 and a few really good ones max qty is 10.
So we don't have to worry about allocation, these rules let every store buy based on their entitlement. When they try to put more in the cart then they should, they get a message "You are requesting to order more than your allocation limit. Please change your requested quantity." I don't know where this comes from.
Some users buy for 5 or more stores which is selected at checkout during payment. This keeps those store owners from having to have a bunch of log ins to keep track of.
We recently openned up Order Management, we call it multi-cart because this enables a store owner to create more than 1 cart by going to order management and create a new order. This makes it much easier for our store owners to manage what they are buying and paying and receiving with out having to call and email our CSR teams.
But now we noticed that some stores are taking advantage of the Multi-cart to buy more that the MAX qty they are allowed. It wouldn't be so bad, but they are buying all the 1 per customer stuff and all the other stores are calling and complaining because they didn't get their share. It really isn't fair.
I was thinking of all the different places to add a SQL check of order history and pending orders. Here is what I cam up with.
ATP - Inventory check
Pro- best place since customer, sku, entitlement, and everything else pretty much happens here. It is right up front.
Con- It doens't have ship-to, so the guys with more than 1 store need to be added as an exception leading sloppy business logic that could change regularly
OrderItemAddCmdImpl and overloading ExtendOrderItemProcessCmd
Pro - Bring ship-to selection up to the front and control everything here.
Con - Not certain overhead will like it.
At checkout
Pro - this also will have everything
Con - I kind of want to reserve this for all payment handling. It is a little dirty to read throught the order lines and to kick back error with SKU.
Have the ERP handle the exception-
Con - I realized we are setup that all Orders ship complete, we would have to change this and don't really want to because there are additional credit card penalties for charges less then amount held on credit.
So, the questions are what are your thoughts on additional pros and cons?
Are there other places that I'm missing that would make more sense?
We might need to create a new CommandTask and then append it to all existing flows.
OR
As the WebSphere Commerce team to build this new logic into the next release of WebSphere Commerce.
So, for this scenario the answer was creating a JDBC Query that will be called when items are added to cart that sums the Qty by sku of pending orders.
When orderitems are added to the cart, the query will return the item in error if exceeded and not add item.
The query will again run at checkout if all orderitems being paid for exceed total qty max by SKU by shipping address on payment page allowing chance for customer to change billing address if we are limiting item max qty by shipping address.

create rules trade prices for over 200

Hi just got to say you are all life savers you know so much.
Ok got a store 1.72 magento and all working ok so I assign a registered person to Trade and they get all the trade prices for trade group for each product.
Problem is or should I say haven't been able to work out.
How do I create this so up to £200 subtotal they get standard prices over gets trade, to stop people buying one top at a time.
I see the discount amount from subtotal but as products they select are random wouldn't be able to calculate that.