docs: changes for next release (#12098)
* docs: changes for next release * generate * generate
This commit is contained in:
@@ -105,11 +105,11 @@ To retrieve the account holder associated with a customer with [Query](!docs!/le
|
||||
const { data: customers } = await query.graph({
|
||||
entity: "customer",
|
||||
fields: [
|
||||
"account_holder.*",
|
||||
"account_holders.*",
|
||||
],
|
||||
})
|
||||
|
||||
// customers.account_holder
|
||||
// customers.account_holders
|
||||
```
|
||||
|
||||
</CodeTab>
|
||||
@@ -123,11 +123,11 @@ import { useQueryGraphStep } from "@medusajs/medusa/core-flows"
|
||||
const { data: customers } = useQueryGraphStep({
|
||||
entity: "customer",
|
||||
fields: [
|
||||
"account_holder.*",
|
||||
"account_holders.*",
|
||||
],
|
||||
})
|
||||
|
||||
// customers.account_holder
|
||||
// customers.account_holders
|
||||
```
|
||||
|
||||
</CodeTab>
|
||||
|
||||
@@ -23,6 +23,14 @@ It holds fields retrieved from the third-party provider, such as:
|
||||
|
||||
A payment provider that supports saving payment methods for customers would create the equivalent of an account holder in the third-party provider. Then, whenever a payment method is saved, it would be saved under the account holder in the third-party provider.
|
||||
|
||||
### Relation between Account Holder and Customer
|
||||
|
||||
The Medusa application creates a link between the [Customer](/references/customer/models/Customer) data model of the [Customer Module](../../customer/page.mdx) and the `AccountHolder` data model of the Payment Module.
|
||||
|
||||
This link indicates that a customer can have more than one account holder, each representing saved payment methods in different payment providers.
|
||||
|
||||
Learn more about this link in the [Link to Other Modules](../links-to-other-modules/page.mdx) guide.
|
||||
|
||||
---
|
||||
|
||||
## Save Payment Methods
|
||||
|
||||
Reference in New Issue
Block a user