> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/bigcommerce-prebuilt-checkout-solution/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/bigcommerce-prebuilt-checkout-solution/use-digital-river-prebuilt-checkout-with-bigcommerce/create-the-prebuilt-checkout-configuration.md).
# Create the Prebuilt Checkout configuration
Create the Prebuilt Checkout configuration needed for using with BigCommerce.
To use Prebuilt Checkout with BigCommerce, provide updated configuration information to integrate the feature. Complete the following tasks to do this.
## Update the Configuration Service
Update the configuration service drop-in scope to include `bigCommerce` data. \
The following sample excerpt from the configuration file shows how this is done:
Use the following values when updating the `drop-in` section of the configuration service for using Prebuilt Checkout with BigCommerce:
| **Attribute** | **Value** |
| ------------------- | ---------------------------------------------------------------------- |
| `bc_auth_token` | Specifies the API key the client created in their BigCommerce store. |
| `bc_store_id` | Specifies the client's BigCommerce store ID. |
| `defaultSkuGroupId` | Specifies the default SKU group used if a skuGroup is not configured. |
## Update the API Key configuration.
Update the client's public and secret API key to include the `partner-id`attribute to specify `BIG_COMMERCE`. Do this from the BigCommerce dashboard as follows:
