> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/payments.md).

# Payments

## Payments

## Payment Methods

Payment methods are the mechanisms used to generate and capture payments for orders. Chord OMS accepts many different payment methods, however the majority of merchants use Stripe, which is Chord's default and preferred payment method.

Chord OMS features the following payment methods:

* Stripe credit card (default, preferred)
* Stripe invoice
* Braintree
* Square
* Store credit
* Tiktok payments
* Pre-paid payments

Orders can have multiple payments from different payment methods. Typically, an order will only have a single payment from a single payment method. The most common exception to this rule is when a customer has store credit that does not cover the total amount of the order. In this case, Chord OMS will apply the available store credit as a partial payment on the order, then capture an additional payment from the customer during checkout.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-1629ed456af1c39c4a9bf61db322e34d41f0ae44%2Fpayments-1.png?alt=media)

### Managing payment methods

Merchants can manage payment methods through the Chord web administration site. Login to the site, click **Settings**, then\*\* Payments\*\*.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-fe5f9159993fd565b86aa0f8ced00cd45e7de335%2Fpayments-2.png?alt=media)

### Multiple payment methods

Chord OMS can be configured to accept multiple payment methods.

For example, one merchant process ala carte and new subscription orders via Stripe, but continues to process legacy subscriptions (i.e. those created on their previous ecommerce platform before migrating to Chord) using Braintree. For example, the screenshots below from the same merchant show multiple subscriptions with different payment methods.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-08f335cdb5f133fac990c9f4d65a29de7b24ca41%2Fpayments-3.png?alt=media)

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-e8884bdf7b013ebafa55ff0d001f4e26ddfc7d45%2Fpayments-4.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/chord-oms/chord-oms-overview/payments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.