diff --git a/docs/financial/OrderAPI.md b/docs/financial/OrderAPI.md
index beb67a2da65e21c5254d6fdd06de82d4805256d1..c37f1db79d0b9354021d0f7b9cde1e074471ade5 100644
--- a/docs/financial/OrderAPI.md
+++ b/docs/financial/OrderAPI.md
@@ -1,3 +1,8 @@
+!!! abstract
+    This area of CiviCRM code and documentation is a work-in-progress. Not all features
+    will be documented and the core code underlying this area may change from version
+    to version.
+
 The Order API is intended to be used as the primary API for adding, updating, and deleting orders.
 
 An 'order' is a non-CiviCRM term that corresponds to how CiviCRM uses its contribution object in terms of handling the full life-cycle of a purchase of memberships, event registrations or making a donation. Unlike most APIs, there is no table directly associated with the Order API.
diff --git a/docs/financial/PaymentAPI.md b/docs/financial/PaymentAPI.md
index 544807ccb83bec2c399b4d0a16fcd15a0def81d4..38eb41ea80b0bee8381ace02aacf36e327aa3c98 100644
--- a/docs/financial/PaymentAPI.md
+++ b/docs/financial/PaymentAPI.md
@@ -1,4 +1,9 @@
-Payment API
+!!! abstract
+    This area of CiviCRM code and documentation is a work-in-progress. Not all features
+    will be documented and the core code underlying this area may change from version
+    to version.
+
+## Payment API
 
 Historically, one recorded a payment against a contribution by changing its payment status, for example from Pending to Completed. 
 
diff --git a/docs/financial/overview.md b/docs/financial/overview.md
index 45a60d6d69a8445ce52dde1fdeb0fb9a28f56790..d700b42a83ece0c11a6e66e18929b0941f2103e8 100644
--- a/docs/financial/overview.md
+++ b/docs/financial/overview.md
@@ -1,3 +1,8 @@
+!!! abstract
+    This area of CiviCRM code and documentation is a work-in-progress. Not all features
+    will be documented and the core code underlying this area may change from version
+    to version.
+
 The financial subsystem in civicrm encompasses:
 
 - contributions