multiversx-payment-handling

Use the `self.call_value()` API to handle EGLD and ESDT payments in MultiversX smart contracts, supporting single, multi, optional, and mixed payment patterns for secure financial transactions.

The best way to accept mixed token payments is processing EGLD and ESDT simultaneously using the unified `self.call_value()` API, which provides robust validation for correct token types and amounts received.

The `self.call_value()` API processes incoming contract payments by capturing the call value and routing EGLD or ESDT tokens to the appropriate contract balances with unified payment handling and validation.

Yes, you need SDK v0.64 or higher to handle ESDT payments in MultiversX, as this version provides the required payment type definitions and best practices for robust contract development.

Yes, you can process optional payments using the `self.call_value()` API, which supports optional payment patterns alongside single, multi, and mixed payments within MultiversX smart contracts.

When using `self.call_value()` for multi-token payments, you must strictly adhere to SDK v0.64+ payment type definitions to avoid validation errors and ensure correct routing of EGLD and ESDT amounts.