--- title: "KOMOJU Changelog" description: "All platform updates and release notes for KOMOJU." url: "https://docs.komoju.com/en/changelog" language: en --- # KOMOJU Changelog ## Subscriptions API: Fixed Billing Dates and Proration > 2026-09-24 Subscriptions can now bill every customer on a fixed day, with an optional prorated first charge for customers who join mid-cycle. ## What Changed Previously, a subscription charged the customer on the day it was created. `POST /subscriptions` now accepts two optional parameters for billing on a fixed day: - `payment_cycle`: sets the billing day. Pass `anchor_date` (`YYYY-MM-DD`), or use `day_of_month` (1–31) for monthly subscriptions, `day_of_week` (1 for Monday to 7 for Sunday) for weekly subscriptions, or `month` with `day_of_month` for yearly subscriptions. `timezone` takes an IANA identifier such as `Asia/Tokyo`. If omitted, the merchant's default timezone is used. - `proration_logic`: sets how the first cycle is charged. - `prorata` immediately charges a prorated amount for the days until the billing date, then charges the full amount from the billing date onward. - `none` charges nothing at signup and charges the full amount on the billing date. Until then, the subscription stays in `awaiting` status. If `payment_cycle` is provided without `proration_logic`, `none` is used. If the billing date is today or in the past, the full amount is charged immediately. Charges run at 09:00 in the applicable timezone. The subscription object now also returns `started_at`, `proration_logic`, and `payment_cycle`. The `status` field can now be `awaiting`. ## Developer Impact Existing subscriptions and requests without `payment_cycle` work as before. To bill all subscribers on the same day, such as the 1st of each month, add `payment_cycle` to new subscription requests. If your integration reads subscription statuses, handle the new `awaiting` status. --- ## Redesigned Settlement Details and Invoices Pages > 2026-09-15 The Settlement Details and Invoices pages in the Merchant Dashboard have a new layout, with full payout breakdowns, invoice previews, and bulk downloads. ## What Changed Two pages in the Merchant Dashboard now use the new dashboard design. To open the Settlement Details page, select any payout row on the Balances & Payouts page. The page shows the full settlement breakdown in one view: - Captured and refunded amounts, processing fees, chargebacks, and KOMOJU Card charges, which add up to the payout amount shown at the top of the page - One section per line item type, with item counts shown as badges - Collapsible sections on mobile, available in English and Japanese ![Settlement Details page showing a paid payout with the About this payout section, captured amounts by payment method, refunded amount, processing fees, and other fees](https://docs.komoju.com/changelog_settlement-details-page.webp) The Invoices page includes: - Search and filters with date presets, including partial matches on invoice ID - Invoice amounts in the list, so you can check a total without opening the PDF - PDF preview before download - Bulk download of multiple selected invoices - A mobile layout for viewing and downloading invoices ![Invoices page with invoice ID search, the Invoice Period filter, invoice amounts, and one invoice selected for download](https://docs.komoju.com/changelog_invoices-page.webp) Invoice PDFs were also updated. Long company names and address lines no longer overlap, and the Japanese invoice layout has been corrected. ## Merchant Impact You can check how a payout was calculated without exporting a CSV. Finding and downloading invoices for accounting also takes fewer steps in the dashboard. Invoice contents and billing are unchanged. --- ## Zero-Amount Authorization for Card Verification > 2026-09-14 KOMOJU now verifies saved cards with a 0 JPY authorization instead of 1 JPY, following Visa and Mastercard guidelines. ## What Changed When KOMOJU verifies a card without charging it, the check now uses a 0 JPY authorization instead of a 1 JPY authorization. This applies, for example, when a card is saved to a customer for subscriptions. Some issuers, such as certain debit card issuers, decline 0 JPY authorizations. For those cards, KOMOJU retries with a 9 JPY authorization and cancels it immediately. Verifications at 0 JPY do not appear in the Merchant Dashboard. The 9 JPY fallback authorizations remain visible, in the same way 1 JPY authorizations were shown before. ## Merchant Impact No integration or configuration changes are needed. Debit and prepaid cardholders who save a card no longer see a temporary 1 JPY deduction or a charge notification. --- ## WeChat Pay In-Store Applications for Physical Terminals > 2026-09-10 Merchants using KOMOJU Terminal can now apply for in-store WeChat Pay acceptance from the dashboard. ## What Changed Merchants with physical storefronts can now apply for WeChat Pay terminal acceptance from the Payment Methods settings page. The application requires in-store compliance verification photos and details. ## Merchant Impact Merchants no longer need to submit a paper application to accept WeChat Pay QR payments from Chinese visitors on their KOMOJU POS terminals. --- ## WooCommerce Plugin v3.3.3: Checkout Descriptions and Callback Fixes > 2026-09-09 Version 3.3.3 of the KOMOJU WooCommerce plugin shows custom payment method descriptions on classic checkout and fixes delayed webhook callbacks. ## What Changed Version 3.3.3 of the official KOMOJU WooCommerce plugin renders custom payment method descriptions in the classic checkout flow. It also fixes an issue where webhook callbacks could be delayed after a merchant account switch. ## Merchant Impact Stores using classic checkout themes can now show customer guidance text directly under each payment method radio button. Webhook callbacks are no longer delayed after switching merchant accounts. --- ## Dedicated Error Code for Insufficient Refund Balances > 2026-09-04 The refund endpoint now returns an insufficient_balance error code when your account does not have enough funds to cover a refund. ## What Changed If your account does not have enough unsettled funds to cover a refund request, `POST /api/v1/payments/{id}/refund` now returns an HTTP 400 error with the code `insufficient_balance`. Previously, this case returned a generic error. ## Developer Impact Your integration can detect `insufficient_balance` and handle it programmatically, for example by alerting your finance team or topping up your reserve. Because the error code is specific, you can tell a balance shortfall apart from a gateway timeout. --- ## Financial Summary Page Replaces Legacy Reports > 2026-09-02 A new Financial Summary page replaces the legacy Reports view, with overview cards, pre-calculated totals, and terminology that matches settlement CSV exports. ## What Changed The Merchant Dashboard has a redesigned Financial Summary page that replaces the legacy Reports view. The new page includes: - Overview cards for Transactions, Refunds, Processing Fees, Settlements, and Bank Transfers - Transaction Summary and Fees & Others sections that use the same terminology as settlement CSV exports - On-demand CSV and Excel exports of all transactions for the selected accounting period ![Financial Summary page showing the Overview cards, the Weekly Breakdown of Bank Transfers, the transaction detail banner, and the Transaction Summary and Fees & Others sections](https://docs.komoju.com/changelog_financial-summary-page.webp) ## Merchant Impact Totals are pre-calculated, so you no longer need to reconcile figures across multiple screens. The legacy Reports page stays available alongside the new page through September 30, 2026, and is retired after that date. --- ## Google Pay 3DS Authentication and Card Network Filtering > 2026-08-31 Google Pay now shows only the card brands enabled on the merchant account and routes payments through full 3D Secure challenges. ## What Changed Google Pay integrations on KOMOJU Hosted Page and Hosted Fields now apply the merchant's card brand configuration and route payments through full 3D Secure challenges. The Google Pay sheet only displays cards from networks enabled on the merchant's account. ## Merchant Impact Customers can no longer select a card brand the merchant does not accept. This prevents checkout errors caused by unsupported card brands. --- ## Chargeback Management Tool and API > 2026-08-19 View disputes, accept chargebacks, and submit defense documentation from the Merchant Dashboard or through the API. ## What Changed KOMOJU has launched the Chargeback Management Tool in the Merchant Dashboard, along with REST API endpoints under `/api/v1/chargebacks`. The release includes: - A dashboard interface for tracking dispute deadlines, reviewing claims, accepting liability, and uploading defense files - Automatic webhook and email notifications for new chargebacks and upcoming deadlines - API support for retrieving dispute records and submitting defense files programmatically ## Merchant Impact Merchants no longer need to manage chargebacks through email and spreadsheets. They can respond to card issuer inquiries faster. Deadline notifications also help reduce disputes lost to missed filing deadlines. --- ## 3D Secure Authentication Migration to Netcetera > 2026-08-01 KOMOJU has moved its 3D Secure authentication to Netcetera in live and test mode, with no merchant changes required. ## What Changed KOMOJU has migrated its 3D Secure (3DS) authentication pipeline to Netcetera in both live mode and test mode. ## Merchant Impact No configuration changes or integration updates are required. Customers see the same checkout challenge flow as before. The new infrastructure also improves gateway uptime and supports a wider range of issuer protocols. --- ## Official WooCommerce Partnership & Core Plugin Launch > 2026-07-28 KOMOJU is now an official WooCommerce partner, with the KOMOJU plugin live on WooCommerce.com for direct installation. ## What Changed KOMOJU is now an official WooCommerce partner, with the KOMOJU plugin live on WooCommerce.com for direct installation. ## Merchant Impact Merchants can install KOMOJU directly from WooCommerce, with built-in security/stability improvements. --- ## Selectable Payment Methods on Payment Links > 2026-07-22 Merchants can restrict a Payment Link to a subset of their active payment methods (e.g., card only) instead of offering all of them. ## What Changed Merchants can restrict a Payment Link to a subset of their active payment methods (e.g., card only) instead of offering all of them. ## Merchant Impact Simplifies checkout for links aimed at specific customer segments. --- ## Auto-Expiring Payment Links > 2026-06-09 Payment Links can now be set to automatically disable after a maximum number of payments or a specific expiration date. ## What Changed Payment Links can now be set to automatically disable after a maximum number of payments or a specific expiration date. ## Merchant Impact Helps merchants manage limited inventory and enforce payment deadlines. --- ## Chargeback Custom Reporting > 2026-06-08 Custom reports inside the Merchant Dashboard to track ongoing disputes, dispute win rates, and pending collection data. ## What Changed Custom reports inside the Merchant Dashboard to track ongoing disputes, dispute win rates, and pending collection data. ## Merchant Impact Gives finance teams reconciliation logs, visibility into open challenge deadlines, and downloadable dispute history. --- ## Payment Links Core UX Improvements > 2026-06-05 Payment Links now support link duplication, auto-opening QR/URL popup after creation, standardized UI patterns, and distinct navigation. ## What Changed Payment Links now support link duplication, an auto-opening QR/URL popup after creation, standardized UI patterns, and separate navigation entry points for Quick Links vs. standard Payment Links. ## Merchant Impact Faster, more consistent link creation and management workflow. --- ## PayPay Intermediate Page Deprecation (Shopify) > 2026-05-21 Removed the intermediate confirmation page shown before redirecting to PayPay on Shopify checkouts. ## What Changed Removed the intermediate confirmation page shown before redirecting to PayPay on Shopify checkouts, for merchants not using PayPay Oversell Protection. ## Merchant Impact Faster checkout redirect intended to improve PayPay conversion on Shopify. --- ## Duplicate Payment Links > 2026-04-28 Merchants can duplicate an existing Payment Link; all details copy over except the title, which gets an auto-appended '(1)'. ## What Changed Merchants can duplicate an existing Payment Link; all details copy over except the title, which gets an auto-appended '(1)' since titles must be unique. ## Merchant Impact Saves time for merchants who repeatedly create similar links. --- ## 3D Secure Challenge Fallbacks for High-Risk Card Payments > 2026-04-16 High-risk card transactions no longer get an automatic rejection; instead, a 3D Secure challenge is triggered, and only transactions that pass proceed. ## What Changed High-risk card transactions no longer get an automatic rejection; instead, a 3D Secure challenge is triggered, and only transactions that pass proceed. ## Merchant Impact Improves checkout success rate for legitimate high-risk-flagged customers. --- ## Merpay Eligibility Extended to Sole Proprietors > 2026-04-15 Merpay is now available to sole proprietors, in addition to corporations. ## What Changed Merpay is now available to sole proprietors, in addition to corporations. ## Merchant Impact Widens Merpay access to individual/small-scale merchants. --- ## Subsidized SMB Pricing for Face-to-Face Payments > 2026-03-09 Small and medium physical-store merchants using KOMOJU terminals can now access a subsidized card rate of 2.4%, down from the standard 2.88% or 3.2%. ## What Changed Small and medium physical-store merchants using KOMOJU terminals can now access a subsidized card rate of 2.4%, down from the standard 2.88% or 3.2%. ## Merchant Impact Lower processing costs for small/medium brick-and-mortar merchants. --- ## Balances & Payouts Merchant UI > 2026-02-25 Redesigned Balances & Payouts page combining payout and settlement views, with more detail on past and upcoming payouts. ## What Changed Redesigned Balances & Payouts page combining payout and settlement views, with more detail on past and upcoming payouts. ## Merchant Impact Clearer visibility into past and upcoming payouts in one place. --- ## One-Click Address Collection on Payment Links > 2026-02-04 Merchants can now collect a customer's address on a Payment Link with a single click, instead of setting up manual custom text fields. ## What Changed Merchants can now collect a customer's address on a Payment Link with a single click, instead of setting up manual custom text fields. ## Merchant Impact Removes the need for manual custom-field setup to collect addresses. --- ## v.2026-01-27 > 2026-01-27 In API version v.2026-01-27 we have adjusted how the api/v1/payments endpoint calculates tax. In API version v.2026-01-27 we have adjusted how the `api/v1/payments` endpoint calculates tax. # Updated Endpoints **Tax calculation changes**: - [POST payments](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments) # Tax Calculation Changes Made changes to how tax is calculated based on the request object, this change was made to make tax more intuitive by only allowing automated calculation to occur when explicitly defined with `auto`. ## `POST Payments` The payments `tax` calculation logic has been changed. - **Return value calculation changes**: - `tax`: Tax is no longer automatically calculated when `tax` field is not included in request, if `tax` is not included in the request the calculated `tax` will be set to `0`. Tax will still be automatically calculated if `tax` is `auto` in the request. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments) --- ## Apple Pay Expanded to API Merchants > 2026-01-14 Apple Pay is now available to merchants using direct API integrations, in addition to Hosted Page, WooCommerce, and Hosted Fields. ## What Changed Apple Pay is now available to merchants using direct API integrations, in addition to its existing availability on Hosted Page, WooCommerce, and Hosted Fields. ## Merchant Impact Expands Apple Pay reach to API-integration merchants; eligibility details linked. --- ## GrabPay Onboarding Deprecation > 2026-01-06 Removed GrabPay from onboarding forms following partner PPRO's sunset notice. ## What Changed Removed GrabPay from onboarding forms following partner PPRO's sunset notice. ## Merchant Impact Relevant to merchants who may have expected GrabPay availability. --- ## v.2025-01-28 > 2025-01-28 In API version v.2025-01-28, we’ve improved how partial captures are represented, expanded the available information on settlements (including a revamped CSV and XLS format), and introduced updates for Platform Model. In API version v.2025-01-28, we’ve improved how partial captures are represented, expanded the available information on settlements (including a revamped CSV and XLS format), and introduced updates for Platform Model. Review this changelog for more information on what endpoints have changed. --- # Updated Endpoints **Partial Captures improvements:** 1. [GET payments](https://docs.komoju.com/#get-payments) 2. [POST payments](https://docs.komoju.com/#post-payments) 3. [GET payments/:id](https://docs.komoju.com/#get-paymentsid) 4. [PATCH payments/:id](https://docs.komoju.com/#patch-paymentsid) 5. [POST payments/:id/capture](https://docs.komoju.com/#post-paymentsidcapture) 6. [POST payments/:id/refund](https://docs.komoju.com/#post-paymentsidrefund) 7. [POST payments/:id/cancel](https://docs.komoju.com/#post-paymentsidcancel) 8. [POST payments/:id/finalize](https://docs.komoju.com/#post-paymentsidfinalize) 9. [GET merchants/merchant_id/payments](https://docs.komoju.com/#get-merchantsmerchant_idpayments) **Settlements & Platform Model improvements:** 1. [GET balances/:id](https://docs.komoju.com/#get-balancesid) 2. [GET settlements](https://docs.komoju.com/#get-settlements) 3. [GET settlements/:id](https://docs.komoju.com/#get-settlementsid) 4. [GET settlements/:id/csv](https://docs.komoju.com/#get-settlementsidcsv) 5. [GET settlements/:id/xls](https://docs.komoju.com/#get-settlementsidxls) # Partial Captures improvements Partial captures are now represented using a new "captures" array on payment object, instead of being shown as partial refunds, simplifying reporting and reconciliation. ## `GET payments` The response object for partially captured payments has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: partially captured payments no longer show a refund for the difference between the authorized amount and captured amount. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/GET/payments) ## `POST payments` The response object for partially captured payments has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments) ## `GET payments/:id` The response object for a partially captured payment has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/GET/payments/%7Bid%7D) ## `PATCH payments/:id` The response object for a partially captured payment has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/PATCH/payments/%7Bid%7D) ## `POST payments/:id/capture` The response object for a partially captured payment has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments/%7Bid%7D/capture) ## `POST payments/:id/refund` The response object for a partially captured payment has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments/%7Bid%7D/refund) ## `POST payments/:id/cancel` The response object for a partially captured payment has been updated. **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments/%7Bid%7D/cancel) ## `POST payments/:id/finalize` The response object for a partially captured payment has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: a refund for the difference between the authorized amount and captured amount is not shown if the payment is a partially captured payment. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/payments/POST/payments/%7Bid%7D/finalize) ## `GET merchants/:merchant_id/payments` The response object for a partially captured payment has been updated. - **Return value changes**: - `amount_refunded`: the refund amount for the difference between the authorized amount and captured amount is no longer included for partially captured payments. - `refunds`: partially captured payments no longer show a refund for the difference between the authorized amount and captured amount. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/platform-model/GET/merchants/%7Bmerchant_id%7D/payments) # Settlements & Platform Model improvements We updated endpoint structures to support the new [Platform Model](https://docs.komoju.com/en/docs/platform-model/platform-model-overview.md), and expanded the available keys to include more settlement data. The formats of the CSV and XLS settlement reports have been changed to include this new data as well. ## `GET balances/:id` Transformed the response to a nested (2D) structure to match the Merchant dashboard's Payout Balance page. - **Renamed keys**: - `balance_total` is now `total_balance_cents`. - **Removed keys**: - `payment_fee_total`, `tax_total`. - **Structural changes**: - Added new `payments`, `refunds`, `platform_model`, `corrections`, `komoju_card_charges` and `misc` sections. - `payments`: - Moved here: `payment_total` now called `captured_amount_total` - New keys: `processing_fees` - `refunds`: - Moved here: - `refund_total` now called `refunded_amount_total_cents` - `refund_fee_total` now called `refund_processing_fees_cents` and includes tax - `refunded_customer_fee_total` now called `refunded_customer_fees_cents` and includes tax - `platform_model` (only available for Platform merchants): - Moved here: `fund_transfer_total_cents` - New keys: `payment_share_total_cents`, `payment_share_refund_total_cents`, `platform_fee_total_cents`, `platform_fee_refund_total_cents`, `submerchant_management_fees_cents`. - `disbursements`: - New keys: `disbursement_amount_total_cents`, `disbursement_fee_total_cents`. - `misc`: - New keys: `clearing_total_cents`, `komoju_card_discount_total_cents`, `chargeback_fixed_fee_total_cents`, `other_fee_adjustments_total_cents` (this is the sum of all fee adjustments and any misc. record types that don't belong in other sections. Refer to the API reference for the exhaustive list). - For each section, added a `total_cents` of each of its amounts. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/settlements/GET/balances/%7Bcurrency%7D) ## `GET settlements` Renamed one key name, added a number of new keys, and made changes to several returned values. - **Renamed keys**: - `amount` is now `settlement_amount_cents` in order to make the key more clear and less generic. - **Added keys**: - NOTE: values for keys ending in `_cents` are returned as integers (not strings); any integers related to fees can be negative integers. - `transaction_amount_cents` - `fee_amount_cents` - `fee_tax_amount_cents` - `fx_currency` - `fx_conversion_rate` - `fx_conversion_amount_cents` - `bank_transfer_fee_amount_cents` - `remittance_amount_cents` - **Return value changes**: - `status`: "automatic_pending" is now returned as "pending". - `settlement_amount_cents` (formerly `amount`): the value of `settlement_amount_cents` is now returned as an integer rather than a string. - `download`: all keys in this section (such as `csv` or `xls`) will show "null" instead of a link if the settlement is cancelled. If the settlement is not cancelled, all links will point to an updated version of the report. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/settlements/GET/settlements) ## `GET settlements/:id` Renamed two key names, added a number of new keys, made changes to several returned values, and transformed the response to a nested (2D) structure to include details for various kinds of payments and fees. - **Renamed keys**: - `amount` is now `settlement_amount_cents` in order to make the key more clear and less generic. - **Removed keys**: - `payment_total` - `payment_fee_total` - `refund_total` - `refund_fee_total` - `refunded_customer_fee_total` - `correction_total` - `tax_total` - `balance_amount` - **Added keys**: - NOTE: values for keys ending in `_cents` are returned as integers (not strings); any integers related to fees can be negative integers. - `transaction_amount_cents` - `fee_amount_cents` - `fee_tax_amount_cents` - `fx_currency` - `fx_conversion_rate` - `fx_conversion_amount_cents` - `bank_transfer_fee_amount_cents` - `remittance_amount_cents` - `payments` - `captured_amount_total_cents` - `processing_fees_cents` - `total_cents` - `refunds` - `refunded_amount_total_cents` - `refund_processing_fees_cents` - `refunded_customer_fees_cents` - `total_cents` - `platform_model` (for platform merchants only) - `fund_transfer_total_cents` - `payment_share_total_cents` - `payment_share_refund_total_cents` - `platform_fee_total_cents` - `platform_fee_refund_total_cents` - `submerchant_management_fees_cents` (for platform merchants only) - `total_cents` - `corrections` - `total_cents` - `komoju_card_charges` - `total_cents` - `disbursements` - `disbursement_amount_total_cents` - `disbursement_fee_total_cents` - `total_cents` - `misc` - `clearing_total_cents` - `komoju_card_discount_total_cents` - `chargeback_fixed_fee_total_cents` - `other_fee_adjustments_total_cents` - this is the sum of all fee adjustments and any misc. record types that don't belong in other sections. Refer to the API reference for the exhaustive list. - `total_cents` - **Return value changes**: - `download`: all keys in this section (such as `csv` or `xls`) will show "null" instead of a link if the settlement is cancelled. If the settlement is not cancelled, all links will point to an updated version of the report. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/settlements/GET/settlements/%7Bid%7D) ## `GET settlements/:id/csv` Updated format of the report. - **Return value changes**: - The format of the returned report has been updated. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/settlements/GET/settlements/%7Bid%7D/csv) ## `GET settlements/:id/xls` Updated format of the report. - **Return value changes**: - The format of the returned report has been updated. [Full API Reference for this endpoint](https://docs.komoju.com/en/api-reference#2025-01-28/tag/settlements/GET/settlements/%7Bid%7D/xls) --- ## Introducing API Versioning > 2025-01-14 We're introducing API Versioning to improve flexibility and reliability—find out more in this changelog post. As KOMOJU service offerings are growing rapidly, we find an increasing need for our API to evolve quickly without compromising stability and smooth integration for our clients. API Versioning will enable us to better communicate the path of changes in our API, as well as empower our clients with choice and flexibility to strategically integrate changes that best fit their needs and compatibility. We will officially support each API version for at least one year, ensuring stability for your integration. API versions will remain operational after that date, but we encourage you to migrate to supported versions as they become available to benefit from new features and increased reliability. Read about how you can develop with API versions [here](https://docs.komoju.com/en/docs/introduction/authentication.md#api-version).