# Checkouts, payment sources, and orders
This section's [checklist items](#integration-checklist) and standards cover how to process [MOR/SOR](/digital-river-api/general-resources/glossary.md#merchant-of-record-seller-of-record-mor-sor)-compliant checkouts, subscriptions, payment sources, and orders.
## Integration checklist
Click any checklist item for information on meeting the [checkouts](#checkouts), [payment sources](#payment-sources), and [orders](#orders)-related integration standards.
### Checkouts
* [ ] [In `POST/checkouts` requests, does your integration provide us with the required product data?](#provide-required-product-information)
* [ ] [In `POST/checkouts` requests, does your integration provide us the required compliance product data?](#provide-required-compliance-product-data)
* [ ] [If you're sending `productDetails` in creating checkout requests, does your integration pass your system's unique product identifier as the object's `id`?](#reference-product-identifier-in-product-details)
* [ ] [If you're sending `productDetails` in creating checkout requests, does your integration reference the associated SKU group by specifying a skuGroupId?](#reference-required-sku-group-in-product-details)
* [ ] [Do you use the `taxInclusive` flag to indicate whether the total cost of an order's items should be treated as tax-inclusive or exclusive?](#indicate-whether-taxes-are-included-in-the-retail-price)
* [ ] [Does your integration provide the customer's public IP address?](#provide-the-customers-public-ip-address)
* [ ] [Do you use your commerce platform's unique order identifier (UUID) as the upstream identifier?](#ensure-the-specified-upstream-identifier-matches-your-order-identifier)
* [ ] [For orders that contain physical products, do you specify `shipTo` and `shipFrom` values?](#supply-required-shipping-address-information)
* [ ] [After Digital River responds to a create or update checkout request, does your integration use the data provided by Digital River to update the commerce system's product and shipping tax data and then ensure that the values in both systems match?](#synchronize-checkout-data)
#### Checkouts with subscriptions
* [ ] [During subscription acquisitions, do you set the charge type to customer-initiated?](#set-charge-type-to-customer-initiated-in-subscription-acquisitions)
* [ ] [When auto-renewing a subscription, do you set the charge type to merchant-initiated?](#set-charge-type-to-merchant-initiated-in-subscription-auto-renewals)
* [ ] [Do you send subscription information for every subscription product or service included in a transaction?](/digital-river-api/general-resources/standards-and-certifications/integration-checklists/checkouts-payment-sources-and-orders.md#send-subscription-information)
* [ ] [After the customer accepts the terms of an auto-renewing subscription, do you pass them to Digital River?](#send-the-subscriptions-terms)
* [ ] [Does your subscription management system generate a subscription identifier during the acquisition process?](/digital-river-api/general-resources/standards-and-certifications/integration-checklists/checkouts-payment-sources-and-orders.md#generate-a-subscription-identifier)
* [ ] [Do you specify a subscription's renewal method?](#specify-a-subscriptions-renewal-method)
* [ ] [During the renewal process, do you send the same billing agreement identifier generated during the subscription's acquisition?](#send-the-billing-agreement-identifier-in-renewals)
* [ ] [If a customer pays for a subscription with Klarna, do you provide the start and end time?](#provide-a-start-and-end-time-for-klarna-funded-subscriptions)
### Payment sources
* [ ] [Do you use Drop-in payments to display available payment methods and create a payment source?](#use-drop-in-to-create-payment-sources)
* [ ] [Do you provide customers the option to save payment information for future use?](#provide-option-to-save-credit-card-for-future-use)
* [ ] [During transaction flows, if customers elect to save payment information for future purchases, do you save the source to their account?](#save-ready-for-storage-payment-sources-to-the-customers-account)
* [ ] [Does the `onSuccess` event fired by Drop-in payments trigger a final step in your checkout process that allows the customer to review all order and tax totals before making the purchase?](#respond-to-on-success-events-and-display-the-order-review-page)
#### Payment sources with subscriptions
* [ ] [When customers acquire an auto-renewing subscription, do Drop-in payments only display payment methods supporting reusability?](#display-reusable-payment-sources)
* [ ] [Do you configure Drop-in payments to display and acquire the customer's acceptance of the combined subscription and payment storage terms?](#acquire-customers-acceptance-of-subscription-and-payment-storage-terms)
* [ ] [Do you save ready-for-storage payment sources to a customer's account?](#save-ready-for-storage-source-to-customers-account)
### Orders
* [ ] [After a customer places an order on the storefront, do you pass the checkout identifier to a `POST/orders` request?](#create-an-order-with-the-checkout-identifier)
* [ ] [Do you use the `POST/orders` response to update the storefront's UI with an order success or order failed message?](#notify-the-customer-of-the-order-status)
* [ ] [Do you use the `POST/orders` response to set the order status in your upstream commerce platform?](#align-order-states)
* [ ] [Do you capture the order's identifier?](#capture-the-orders-identifier)
* [ ] [Do you capture the order's payment status?](#capture-the-orders-payment-state)
* [ ] [Do you capture the order's fraud status?](#capture-the-orders-fraud-state)
* [ ] [Do you listen for and handle the order accepted event?](#listen-for-and-handle-the-order-accepted-event)
* [ ] [Do you listen for and handle order failed events?](#consume-the-event-emitted-when-an-order-fails)
#### Orders with subscriptions
* [ ] [Do you persist in the billing agreement identifier generated during the acquisition process for auto-renewing subscriptions?](/digital-river-api/general-resources/standards-and-certifications/integration-checklists/checkouts-payment-sources-and-orders.md#persist-the-billing-agreement-identifier)
## Integration standards
The checkout, payment source, and order standards that apply to your integration depend on which of the above checklists you're using.
### Provide required product data
When [sending product data in create checkout requests](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md#sending-product-data) each [`items[]`](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md) must include a [SKU ](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/skus)identifier or a [`productDetails`](/digital-river-api/product-management/skus.md#product-details) object. Each line item in the request must also have a defined [price or aggregate price](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items/price-of-an-item.md) and a [quantity](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md#creating-items).
### Provide required compliance product data
When [associating SKU groups with upstream product data in create checkout requests](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md#send-basic-data-in-product-details-and-compliance-data-in-sku-groups) each [`items[]`](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md) must include `productDetails` and within that object, you must specify a `skuGroupId`.
### Reference product identifier in product details
If you're sending [`productDetails`](/digital-river-api/product-management/using-product-details.md) in [create checkout requests](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts#checkouts-1), your integration should pass your system's unique product identifier as the object's `id`.
For more information, refer to the [sending product data in checkouts](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md#sending-product-data) section on the [Describing line items page](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md).
### Reference required SKU group in product details
If you're sending [`productDetails`](/digital-river-api/product-management/using-product-details.md) in [create checkout requests](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts#checkouts-1), your integration must reference the product's associated [SKU group](/digital-river-api/product-management/setting-up-sku-groups.md). You do this by specifying a `skuGroupId` in the `productDetails` object.
For more information, refer to the [sending product data in checkouts](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md#sending-product-data) section on the [Describing line items page](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items.md).
### Indicate whether taxes are included in the retail price
When [building a checkout](/digital-river-api/integration-options/checkouts/creating-checkouts.md), use the `taxInclusive` flag to indicate whether the [price of items](/digital-river-api/integration-options/checkouts/creating-checkouts/describing-the-items/price-of-an-item.md) in an order should be treated as [tax-inclusive or exclusive](/digital-river-api/integration-options/checkouts/creating-checkouts/configuring-taxes.md#setting-tax-inclusive-prices).
### Provide the customer's public IP address
When [building a checkout](/digital-river-api/integration-options/checkouts/creating-checkouts.md), provide the IP address of the customer's browser used to place the order.
### Ensure the specified upstream identifier matches your order identifier
For tracking purposes, specify an [upstream identifier](/digital-river-api/integration-options/checkouts/creating-checkouts/providing-an-upstream-identifier.md) during the [checkout process](/digital-river-api/integration-options/checkouts/creating-checkouts.md) that matches the identifier of the corresponding order in your commerce platform.
### Supply required shipping address information
Orders that contain [physical products](/digital-river-api/product-management/creating-and-updating-skus.md#how-products-are-specified-as-physical-or-digital) must provide [ship from](/digital-river-api/integration-options/checkouts/creating-checkouts/providing-address-information.md#ship-from-requirements) and [ship to](/digital-river-api/integration-options/checkouts/creating-checkouts/providing-address-information.md#ship-to-requirements) address information.
### Synchronize checkout data
Each time you create or update a checkout, [use the response from the Checkouts API](/digital-river-api/integration-options/checkouts/creating-checkouts.md) to update price, fee, and tax information in the upstream commerce platform. These updates should be performed for the entire transaction and each line item. This ensures that the values in your system stay in sync with those in our system.
Additionally, you should display these response values in your interface so customers can review tax and product totals during the checkout process.
### Set charge type to customer-initiated in subscription acquisitions
Since the customer actively participates in a subscription acquisition, you should set [`chargeType`](/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md) to [`customer_initiated`](/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md#customer-initiated).
### Set charge type to merchant initiated in subscription auto-renewals
During a subscription's autorenewal, the customer is not an active participant. As a result, when [building a checkout](/digital-river-api/integration-options/checkouts/creating-checkouts.md) to process an autorenewal, you should set [`chargeType`](/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md) to [`merchant_initiated`](/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md#merchant-initiated).
### Send subscription information
Any transaction that includes a recurring product or service must provide information that describes that subscription. So, when [building a checkout](/digital-river-api/integration-options/checkouts/creating-checkouts.md), provide these details in the [`subscriptionInfo`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#setting-subscription-information) hash table.
### Send the subscription's terms
For [auto-renewing subscriptions](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#auto-renewal), you must display the subscription's terms and acquire the customer's active acceptance of them. So, before [converting a checkout to an order](/digital-river-api/order-management/creating-and-updating-an-order.md#creating-an-order-with-the-checkout-identifier), pass these agreed-upon terms in the checkout's [`terms`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#terms) parameter. This ensures that they are recorded in the [billing agreement](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#billing-agreement-identifier).
### Generate a subscription identifier
During the acquisition process, you can optionally generate a unique subscription identifier and assign it to [`subscriptionId`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#subscription-identifier).
### Specify a subscription's renewal method
For every recurring product or service, you must use the [`autoRenewal`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#auto-renewal) parameter to tell us whether the subscription is automatically or manually renewed.
### Send the billing agreement identifier in renewals
During the renewal process, send the [`billingAgreementId`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#billing-agreement-identifier) generated during the subscription's acquisition.
### Provide a start and end time for Klarna-funded subscriptions
When acquiring or renewing a subscription with the [Klarna ](/digital-river-api/payments/payment-integrations-1/digitalriver.js/payment-methods/klarna.md)payment method, you must [provide a start and end time](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#start-and-end-time).
### Use Drop-in to display available payment methods and create a source
[Drop-in payments](/digital-river-api/payments/payment-integrations-1/drop-in.md) are our all-in-one solution for handling payments and ensuring compliance. We recommend you use this solution as a quick and easy way to start accepting payments.
During the checkout experience, you can use the [configurable Drop-in object](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md) to present available payment methods and safely and securely capture a customer's payment details. The [payment source](/digital-river-api/payments/payment-sources.md) returned in the [`onSuccess` event](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#onsuccess) can then be [attached to the checkout](/digital-river-api/payments/payment-sources/using-the-source-identifier.md#attaching-sources-to-checkouts) before the customer arrives on your order review page.
### Provide option to save payment information for future use
During checkout flows, we recommend you allow customers to save their payment information for future transactions. When [building your payment workflows](/digital-river-api/integration-options/checkouts/building-you-workflows.md) for [one-off](/digital-river-api/integration-options/checkouts/building-you-workflows.md#credit-card-details-saved-by-customer-during-checkout) and [subscription](/digital-river-api/integration-options/checkouts/building-you-workflows.md#customer-enters-credit-card-details-during-subscription-acquisition-checkout) purchases, you can [configure Drop-in payments to present the save payment option](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#optional-allowing-the-customer-to-save-their-payment-details) to customers.
### Save ready-for-storage payment sources to the customer's account
In the [`onSuccess`](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#onsuccess) event, if [`readyForStorage`](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#optional-allowing-the-customer-to-save-their-payment-details) returns `true` or `mandate` is populated, then the customer agrees to save that transaction's payment information for future use. Your integration should [attach the payment source to the customer's record](/digital-river-api/payments/payment-sources/using-the-source-identifier.md#attaching-sources-to-customers).
### Respond to on success event and display the order review page
Whenever [Drop-in payments](/digital-river-api/payments/payment-integrations-1/drop-in.md) successfully create a [payment source](/digital-river-api/payments/payment-sources.md), we send you the [`onSuccess` event](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#onsuccess). Once you receive this event, redirect the customer to the order review page. The customer can review the order's details before deciding whether to purchase.
### Display reusable payment sources
When a customer purchases an auto-renewing subscription, the payment methods that [Drop-in payments](/digital-river-api/payments/payment-integrations-1/drop-in.md) display must [support recurring transactions](/digital-river-api/payments/payment-sources.md#reusable-or-single-use). To ensure that Drop-in only displays [reusable payment methods](/digital-river-api/payments/payment-integrations-1/drop-in.md#supported-payment-methods), set [`autoRenewal`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#auto-renewal) to `true` in a `POST/checkouts` or `POST/checkouts/{id}` request. You then use Drop-in's configurable [`options`](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#drop-in-options) to set `showTermsOfSaleDisclosure` to `true`.
### Acquire customer's acceptance of subscription and payment storage terms
When acquiring an auto-renewing subscription, customers must agree to save the transaction's payment source to their account so that it can be applied to renewals. So, you must configure [Drop-in payments](/digital-river-api/payments/payment-integrations-1/drop-in.md) to display the combined subscription save payment agreement terms and then acquire the customer's active acceptance.
You do this by first setting [`autoRenewal`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#auto-renewal) to `true` in a `POST/checkouts` or `POST/checkouts/{id}` request. You then use Drop-in's configurable [`options`](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#drop-in-options) to set `showTermsOfSaleDisclosure` to `true`.
### Save ready for storage source to customer's account
When the [`onSuccess`](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#onsuccess) event returns a source that is [`readyForStorage`](/digital-river-api/payments/payment-integrations-1/drop-in/drop-in-integration-guide.md#optional-allowing-the-customer-to-save-their-payment-details), you should save the source to the customer's account. This operation flips its `reusable` value to `true`. As a result, the source can be used in [merchant-initiated](/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md#merchant-initiated) subscription auto-renewals.
### Create an order with the checkout identifier
After you display the review order page to the customer and the customer actively accepts Digital River's [disclosure terms](/digital-river-api/developer-resources/reference/digitalriver-object.md#digitalriver-compliance-getdetails-businessentitycode-locale) and then submits the order on the storefront, you should [convert the checkout to an order](/digital-river-api/order-management/creating-and-updating-an-order.md#creating-an-order-with-the-checkout-identifier).\
\
Digital River creates an [order ](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/orders/order-basics)based on the data in a [Checkout](/digital-river-api/integration-options/checkouts.md). Providing `checkoutId` in the payload of `POST/orders` acts primarily as a call to authorize payment and trigger a fraud review.
### Notify the customer of the order status
When a customer uses a [synchronous payment method](/digital-river-api/payments/payment-sources.md#synchronous-or-asynchronous) such as a [credit card](/digital-river-api/payments/payment-sources/handling-credit-card-sources.md) to pay for a transaction, the [`POST /orders` request](/digital-river-api/order-management/creating-and-updating-an-order.md#creating-an-order-with-the-checkout-identifier) almost always immediately returns an [accepted](/digital-river-api/order-management/creating-and-updating-an-order.md#accepted) or [failed](/digital-river-api/order-management/creating-and-updating-an-order.md#409-conflict) order. When the order succeeds, direct the customer to the "Thank you" page. If the order fails, use the error's `message` to inform the customer of the issue through the user interface.
### Capture the order's identifier
When the [`POST /orders` response](/digital-river-api/order-management/creating-and-updating-an-order.md#processing-the-post-orders-response) returns a [`201 Created`](/digital-river-api/order-management/creating-and-updating-an-order.md#201-created) status code, retrieve the order's `id` from the payload and use that value to set the corresponding attribute in the upstream commerce platform's order.
### Align order states
Use the [`POST /orders` response](/digital-river-api/order-management/creating-and-updating-an-order.md#processing-the-post-orders-response) to set the status of the upstream commerce platform's order.
| `POST/orders` response | Due to... | Ready to fulfill? |
| ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| [`409 Conflict`](/digital-river-api/order-management/creating-and-updating-an-order.md#409-conflict) | a [payment authorization failure](/digital-river-api/order-management/creating-and-updating-an-order.md#payment-authorization-failure) | No |
| [`409 Conflict`](/digital-river-api/order-management/creating-and-updating-an-order.md#409-conflict) | a [fraud review failure](/digital-river-api/order-management/creating-and-updating-an-order.md#fraud-review-failure) | No |
| [`201 Created`](/digital-river-api/order-management/creating-and-updating-an-order.md#201-created) | a [pending payment](/digital-river-api/order-management/creating-and-updating-an-order.md#pending-payment) | No |
| [`201 Created`](/digital-river-api/order-management/creating-and-updating-an-order.md#201-created) | an [in-process secondary fraud review](/digital-river-api/order-management/creating-and-updating-an-order.md#in-review) | No |
| [`201 Created`](/digital-river-api/order-management/creating-and-updating-an-order.md#201-created) | an [accepted order](/digital-river-api/order-management/creating-and-updating-an-order.md#accepted) | Yes |
### Capture the order's payment state
When the [`POST /orders response`](/digital-river-api/order-management/creating-and-updating-an-order.md#processing-the-post-orders-response) returns a [`201 Created`](/digital-river-api/order-management/creating-and-updating-an-order.md#201-created) status code, retrieve `charges[].state` from the payload and use that value to set the corresponding attribute in the upstream commerce platform's order.
For [`409 Conflict` errors generated by a payment authorization failure](/digital-river-api/order-management/creating-and-updating-an-order.md#payment-authorization-failure) set the commerce platform's order payment status to failed.
### Capture the order's fraud state
When the [`POST /orders response`](/digital-river-api/order-management/creating-and-updating-an-order.md#processing-the-post-orders-response) returns a [`201 Created`](/digital-river-api/order-management/creating-and-updating-an-order.md#201-created) status code, retrieve `fraudState` from the payload and use that value to set the corresponding attribute in the upstream commerce platform's order.
For [`409 Conflict` errors generated by a fraud review failure](/digital-river-api/order-management/creating-and-updating-an-order.md#fraud-review-failure) set the commerce platform's order fraud status to blocked.
### Listen for and handle the order accepted event
We send the [`order.accepted`](/digital-river-api/order-management/creating-and-updating-an-order.md#listening-for-the-order-accepted-event) event when Digital River successfully authorizes payment and completes its fraud review. This event indicates that the order is ready to be fulfilled. Upon receipt, retrieve `state`, `fraudState`, and `charges[].state` from the payload and use these values to update the corresponding attributes in the upstream commerce platform's order.
### Listen for and handle order failed events
An asynchronous payment authorization failure triggers an [`order.charge.failed`](/digital-river-api/order-management/creating-and-updating-an-order.md#the-payment-failure-event) event. When Digital River asynchronously detects an anomaly during its fraud review or the customer is determined to be on the [Denied Persons List](https://www.bis.doc.gov/index.php/policy-guidance/lists-of-parties-of-concern/denied-persons-list), we send an [`order.blocked`](/digital-river-api/order-management/creating-and-updating-an-order.md#the-fraud-review-failure-event) event.
Upon receipt of either event, retrieve `state`, `fraudState`, and `charges[].state` from the payload and use these values to update the corresponding attributes in the upstream commerce platform's order.
### Persist the billing agreement identifier
For each subscription product or service you create, store the [`billingAgreementId`](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#billing-agreement-identifier) that Digital River generates so that it can be sent in the renewal request.
## API interfaces
| Documentation | Direct API | PHP SDK |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| [Checkouts](/digital-river-api/integration-options/checkouts.md) | [Checkouts](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts) | [Checkouts](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/Checkout.md) |
| [Sources](/digital-river-api/payments/payment-sources.md) | [Sources](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/sources) | [Sources](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/Source.md) |
| [Orders](#orders) | [Orders](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/orders) | [Orders](https://github.com/DigitalRiver/digital-river-php/blob/main/docs/Model/Order.md) |
| [DigitalRiver.js](https://github.com/DigitalRiver/GitBook/blob/Digital-River-API-latest/payments/payment-integrations-1/digitalriver.js#getting-started) | | |
| [DigitalRiver.js Drop-in](/digital-river-api/payments/payment-integrations-1/drop-in.md) | | |
| [Events](/digital-river-api/order-management/events-and-webhooks-1/events-1.md): order.accepted, order.review\_opened, order.pending\_review, order.pending\_payment, order.blocked, order.charge.failed, order.complete | | |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.digitalriver.com/digital-river-api/general-resources/standards-and-certifications/integration-checklists/checkouts-payment-sources-and-orders.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.