# Send the Payload for Authorization
source: https://developer.mastercard.com/mastercard-checkout-solutions/tutorial/integrate_apis_guestcheckout/step5/index.md

## Step 5. Send the Payload for Authorization {#step-5-send-the-payload-for-authorization}

When the consumer submits the order, send the decrypted payload for authorization.

For tokenized transactions, the response payload fields are passed in a Payment Authorization request as follows:

| Solution |                                                                                                                    Description                                                                                                                     |
|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **DSRP** | PAN with the **paymentToken** value, DE 104(Digital Payment Data), sub-element 001 (Digital Payment Cryptogram) with the **dynamicDataValue** and Date Expiration (DE14) with **tokenExpirationMonth** and **tokenExpirationYear** in YYMM format. |

Note: The API specification does not define requirements for transaction processing. For more information about DSRP transactions, refer to:

* [DSRP --- Acquirer Implementation Guide](https://techdocs.mastercard.com/bundle/m_DAIG)
* [AN3363 --- Mandatory Use of Digital Payment Data Field for Remote Commerce Transactions with Cryptograms](https://techdocs.mastercard.com/bundle/m_AN3363/page/jvw1585260985294.html)