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

## Step 8: Send the Payload for Authorization {#step-8-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), subelement 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://trc-techresource.mastercard.com/r/bundle/m_an5843/page/z/ndg1634167211641.html)
* [AN3363 --- Mandatory Use of Digital Payment Data Field for Remote Commerce Transactions with Cryptograms](https://trc-techresource.mastercard.com/r/bundle/m_an3363_en-us/page/d/en-US/jvw1585260985294.html)