> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/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/commerce-api/payments/payments-solutions/drop-in.md).

# Drop-in payments

Drop-in payments are our all-in-one solution for accepting payments and ensuring compliance. They are a quick way to start accepting payments easily.

Use Drop-in payments as your payment method solution if you want:

* To receive newly supported payment methods automatically without deploying code
* Out-of-the-box support for [PSD2 and SCA](/commerce-api/payments/psd2-and-sca.md)
* To ensure compliance for transactions and payment method collection/usage

{% embed url="<https://vimeo.com/500071413>" fullWidth="false" %}

Drop-in payments reference the DigitalRiver.js library and provide a default look and feel that offers various levels of customization. Drop-in payments automatically display supported payments based on data collected during the cart session. Adding a new payment method does not require additional implementation effort but may require additional configuration steps.

For a list of payment methods supported by Drop-in payments, see [Supported payment methods](/commerce-api/payments/supported-payment-methods.md).

## Getting started

Learn how to integrate [our supported payment methods](/commerce-api/payments/supported-payment-methods.md) into your app or website using the [Drop-in payments integration guide](/commerce-api/payments/payments-solutions/drop-in/drop-in-integration-guide.md) and the [Drop-in payments builder](https://drapi.io/drop-in-builder/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/commerce-api/payments/payments-solutions/drop-in.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.