Paymint Notion Database — Recommended Schema
Prerequisite: Read ../mmk-shared/SKILL.md for auth, global flags, and error handling.
Related: mmk-paymint-notion-invoice — Batch send workflow that uses this schema.
This skill shows the recommended Notion database schema for Paymint invoice lifecycle tracking. Present the appropriate tier based on user needs.
Design Tiers
Minimal (11 properties)
Just enough for the mmk-paymint-notion-invoice recipe. Use this when the user only needs to send invoices and track basic results.
| Property |
Type |
Category |
Notes |
| (title) |
title |
Input |
Descriptive label (e.g., "김철수 - 3월 워크샵") |
| 고객명 |
rich_text |
Input |
Recipient name (maps to --name) |
| 연락처 |
phone_number |
Input |
Korean mobile number (maps to --phone) |
| 결제금액 |
number |
Input |
Invoice amount in KRW (maps to --amount) |
| 청구사유 |
rich_text |
Input |
Product/service description (maps to --product) |
| 안내메시지 |
rich_text |
Input |
Invoice message (maps to --message) |
| 유효기간 |
date |
Input |
Expiry date (YYYY-MM-DD). Default: 7 days from send |
| 결제상태 |
select |
Status |
Options: 미결제, 청구완료, 발송실패, 결제완료, 취소 |
| 청구서ID |
rich_text |
Result |
bill_id from send response |
| 발송결과코드 |
rich_text |
Result |
Result code ("0000" = success) |
| ShortURL |
url |
Result |
Payment link |
Full (31 properties)
Complete invoice lifecycle tracking including payment callbacks and cancellations. Use this for production databases that need to track the full payment flow.
1. Input Fields
Properties the user fills in before sending invoices.
| Property |
Type |
Notes |
| (title) |
title |
Descriptive label (e.g., "김철수 - 3월 워크샵"). Row identifier in Notion list view. |
| 고객명 |
rich_text |
Recipient name (maps to --name) |
| 연락처 |
phone_number |
Korean mobile number (maps to --phone) |
| 결제금액 |
number |
Invoice amount in KRW (maps to --amount) |
| 청구사유 |
rich_text |
Product/service description (maps to --product) |
| 안내메시지 |
rich_text |
Invoice message (maps to --message) |
| 유효기간 |
date |
Expiry date (YYYY-MM-DD). Default: 7 days from send date if empty |
| 이메일 |
email |
Optional: recipient email for records |
2. Status & Send Result Fields
Written by the mmk-paymint-notion-invoice recipe after sending.
| Property |
Type |
Notes |
| 결제상태 |
select |
미결제 / 청구완료 / 발송실패 / 결제완료 / 취소 |
| 청구서ID |
rich_text |
bill_id from send response. Must be rich_text, NOT title (title has update restrictions). |
| 발송결과코드 |
rich_text |
Result code ("0000" = success) |
| 발송결과메시지 |
rich_text |
Human-readable result message |
| ShortURL |
url |
Payment link sent to customer |
| CallbackURL |
url |
Webhook callback URL (if configured) |
결제상태 Options
| Option |
Meaning |
Set by |
미결제 |
Pending — invoice not yet sent |
Initial state |
청구완료 |
Invoiced — send succeeded |
Recipe write-back |
발송실패 |
Failed — send error |
Recipe write-back |
결제완료 |
Paid — customer completed payment |
Payment callback |
취소 |
Cancelled/refunded |
Cancel operation |
3. Payment Result Fields
Populated by the payment system callback when the customer pays. The recipe does NOT write these — they come from the payment gateway webhook.
| Property |
Type |
Notes |
| 결제수단 |
select |
Payment method (card, transfer, etc.) |
| 승인번호 |
rich_text |
Approval number |
| 승인금액 |
number |
Approved amount |
| 승인일시 |
rich_text |
Approval datetime |
| 카드/계좌번호 |
rich_text |
Masked card/account number |
| 카드/은행코드 |
rich_text |
Card/bank code |
| 카드/은행명 |
rich_text |
Card/bank name |
| 매입사코드 |
rich_text |
Acquirer code |
| 매입사명 |
rich_text |
Acquirer name |
| 할부개월 |
rich_text |
Installment months |
4. Cancel Fields
Populated on cancel/refund operations.
| Property |
Type |
Notes |
| 취소결과코드 |
rich_text |
Cancel result code |
| 취소결과메시지 |
rich_text |
Cancel result message |
| 취소일시 |
rich_text |
Cancel datetime |
| 원거래승인번호 |
rich_text |
Original approval number |
5. Meta Fields
| Property |
Type |
Notes |
| 메모 |
rich_text |
Internal notes |
| 생성일 |
created_time |
Auto-set by Notion |
| 수정일 |
last_edited_time |
Auto-set by Notion |
Important Design Notes
- Title is a descriptive label, not a data field. Use it for human-readable row identification in Notion views (e.g., "김철수 - 3월 워크샵"). The title property has update restrictions in the Notion API, so never use it for write-back targets like 청구서ID.
- 고객명 is rich_text, not title. This keeps the customer name as a separate queryable and writable field that the invoice recipe can reliably map.
- 청구서ID must be rich_text. The recipe writes bill_id here after sending. If this were title type, the write-back would fail.
- Category 3 (Payment Result) and 4 (Cancel) fields are populated by external systems (payment gateway callbacks), not by the recipe. Include them only if your system has webhook integration.
- 결제상태 select options cover the full lifecycle: pending → invoiced → paid (or failed/cancelled). The invoice recipe maps
미결제 as the "pending" filter and 청구완료/발송실패 as success/failure write-back values.
See Also
1---2name: mmk-paymint-notion-schema3description: Recommended Notion database schema for Paymint invoice tracking. Triggers on "paymint notion schema", "paymint database setup", "invoice database design", "paymint notion template", "paymint db schema".4---56# Paymint Notion Database — Recommended Schema78> **Prerequisite:** Read [`../mmk-shared/SKILL.md`](../mmk-shared/SKILL.md) for auth, global flags, and error handling.9> Related: [`mmk-paymint-notion-invoice`](../mmk-paymint-notion-invoice/SKILL.md) — Batch send workflow that uses this schema.1011This skill shows the recommended Notion database schema for Paymint invoice lifecycle tracking. Present the appropriate tier based on user needs.1213## Design Tiers1415### Minimal (11 properties)1617Just enough for the [`mmk-paymint-notion-invoice`](../mmk-paymint-notion-invoice/SKILL.md) recipe. Use this when the user only needs to send invoices and track basic results.1819| Property | Type | Category | Notes |20|----------|------|----------|-------|21| (title) | title | Input | Descriptive label (e.g., "김철수 - 3월 워크샵") |22| 고객명 | rich_text | Input | Recipient name (maps to `--name`) |23| 연락처 | phone_number | Input | Korean mobile number (maps to `--phone`) |24| 결제금액 | number | Input | Invoice amount in KRW (maps to `--amount`) |25| 청구사유 | rich_text | Input | Product/service description (maps to `--product`) |26| 안내메시지 | rich_text | Input | Invoice message (maps to `--message`) |27| 유효기간 | date | Input | Expiry date (YYYY-MM-DD). Default: 7 days from send |28| 결제상태 | select | Status | Options: `미결제`, `청구완료`, `발송실패`, `결제완료`, `취소` |29| 청구서ID | rich_text | Result | bill_id from send response |30| 발송결과코드 | rich_text | Result | Result code ("0000" = success) |31| ShortURL | url | Result | Payment link |3233### Full (31 properties)3435Complete invoice lifecycle tracking including payment callbacks and cancellations. Use this for production databases that need to track the full payment flow.3637---3839## 1. Input Fields4041Properties the user fills in before sending invoices.4243| Property | Type | Notes |44|----------|------|-------|45| (title) | title | Descriptive label (e.g., "김철수 - 3월 워크샵"). Row identifier in Notion list view. |46| 고객명 | rich_text | Recipient name (maps to `--name`) |47| 연락처 | phone_number | Korean mobile number (maps to `--phone`) |48| 결제금액 | number | Invoice amount in KRW (maps to `--amount`) |49| 청구사유 | rich_text | Product/service description (maps to `--product`) |50| 안내메시지 | rich_text | Invoice message (maps to `--message`) |51| 유효기간 | date | Expiry date (YYYY-MM-DD). Default: 7 days from send date if empty |52| 이메일 | email | Optional: recipient email for records |5354## 2. Status & Send Result Fields5556Written by the [`mmk-paymint-notion-invoice`](../mmk-paymint-notion-invoice/SKILL.md) recipe after sending.5758| Property | Type | Notes |59|----------|------|-------|60| 결제상태 | select | `미결제` / `청구완료` / `발송실패` / `결제완료` / `취소` |61| 청구서ID | rich_text | bill_id from send response. Must be rich_text, NOT title (title has update restrictions). |62| 발송결과코드 | rich_text | Result code ("0000" = success) |63| 발송결과메시지 | rich_text | Human-readable result message |64| ShortURL | url | Payment link sent to customer |65| CallbackURL | url | Webhook callback URL (if configured) |6667### 결제상태 Options6869| Option | Meaning | Set by |70|--------|---------|--------|71| `미결제` | Pending — invoice not yet sent | Initial state |72| `청구완료` | Invoiced — send succeeded | Recipe write-back |73| `발송실패` | Failed — send error | Recipe write-back |74| `결제완료` | Paid — customer completed payment | Payment callback |75| `취소` | Cancelled/refunded | Cancel operation |7677## 3. Payment Result Fields7879Populated by the payment system callback when the customer pays. The recipe does NOT write these — they come from the payment gateway webhook.8081| Property | Type | Notes |82|----------|------|-------|83| 결제수단 | select | Payment method (card, transfer, etc.) |84| 승인번호 | rich_text | Approval number |85| 승인금액 | number | Approved amount |86| 승인일시 | rich_text | Approval datetime |87| 카드/계좌번호 | rich_text | Masked card/account number |88| 카드/은행코드 | rich_text | Card/bank code |89| 카드/은행명 | rich_text | Card/bank name |90| 매입사코드 | rich_text | Acquirer code |91| 매입사명 | rich_text | Acquirer name |92| 할부개월 | rich_text | Installment months |9394## 4. Cancel Fields9596Populated on cancel/refund operations.9798| Property | Type | Notes |99|----------|------|-------|100| 취소결과코드 | rich_text | Cancel result code |101| 취소결과메시지 | rich_text | Cancel result message |102| 취소일시 | rich_text | Cancel datetime |103| 원거래승인번호 | rich_text | Original approval number |104105## 5. Meta Fields106107| Property | Type | Notes |108|----------|------|-------|109| 메모 | rich_text | Internal notes |110| 생성일 | created_time | Auto-set by Notion |111| 수정일 | last_edited_time | Auto-set by Notion |112113---114115## Important Design Notes116117- **Title is a descriptive label**, not a data field. Use it for human-readable row identification in Notion views (e.g., "김철수 - 3월 워크샵"). The title property has update restrictions in the Notion API, so never use it for write-back targets like 청구서ID.118- **고객명 is rich_text**, not title. This keeps the customer name as a separate queryable and writable field that the invoice recipe can reliably map.119- **청구서ID must be rich_text.** The recipe writes bill_id here after sending. If this were title type, the write-back would fail.120- **Category 3 (Payment Result) and 4 (Cancel) fields** are populated by external systems (payment gateway callbacks), not by the recipe. Include them only if your system has webhook integration.121- **결제상태 select options** cover the full lifecycle: pending → invoiced → paid (or failed/cancelled). The invoice recipe maps `미결제` as the "pending" filter and `청구완료`/`발송실패` as success/failure write-back values.122123## See Also124125- [mmk-shared](../mmk-shared/SKILL.md) — Auth, global flags, error handling126- [mmk-paymint-notion-invoice](../mmk-paymint-notion-invoice/SKILL.md) — Batch send workflow using this schema127- [mmk-notion-database](../mmk-notion-database/SKILL.md) — Schema, query, insert, update commands128- [mmk-paymint](../mmk-paymint/SKILL.md) — License Resolution, Error Patterns, all Paymint commands
magic-meal-kits