The hosted payment page went out looking almost identical to the merchant's site: same fonts, same spacing, same quiet palette. In design review someone pointed at the little row of card and security marks near the bottom and called it visual noise. We agreed. On a screen that clean it was the one ugly thing, so out it went.
Then people started dropping at the card step. No failed payments, no errors, just customers who reached the form and walked away from it.
Clicking through the flow on a plain phone made it obvious. The page sat on the merchant's domain, wore the merchant's brand, and said nothing about who was actually going to receive the card number. We had deleted the only element that answered the question every buyer asks silently right there: is it safe to type this here.
The fix was small. The cost was the weeks before it, with the client reasonably convinced their payment provider was the problem.
Since then we treat the trust row on a payment screen the way we treat the amount: content, not decoration. If a review wants it gone for being unattractive, fine, but it has to come back as something that answers the same question, not as emptier space.
You probably have your own version of this, something you pulled off a page for looking cluttered and quietly missed afterwards.