What key functionality is prevented for merchants using standard platforms that create payments directly on their platform with destination payments?

The functionality that is prevented for merchants using standard platforms that create payments directly on their platform with destination payments is the ability to issue refunds from their Stripe dashboards.

When payments are processed through a standard platform that acts as an intermediary, those transactions are attributed to the platform rather than directly to the merchant. As a result, the platform may handle payment management, which can include the authority over issuing refunds. The merchants are then limited in their ability to manage those specific transactions directly. This setup typically means that any refund requests must go through the platform, rather than being managed through the merchants' own dashboards.

In contrast, aggregated reporting, response capabilities for chargebacks, and control over Radar rules generally remain intact for merchants, as those aspects can still be managed within their own Stripe accounts even when using a platform for processing payments. The design is structured to ensure that each party fulfills their role without encroachment into the other's administrative space in payment processing.