An order screen can show that a payment was authorized without establishing that the funds were captured. The merchant also needs to explain what that status permits its own order process to do.
Buyers evaluating OceanBase or another critical order database should preserve those distinctions in the application record. The database can support the merchant’s accepted state and relationships, while authorization, capture, and fulfillment still have their own responsible services and evidence.
Identify what the order’s payment label actually means
Begin with a particular order flow. Ask whether the displayed label means that a payment request was submitted, an authorization exists, capture completed, or another defined condition was observed.
Those labels should be understandable to staff and customers without requiring them to reconstruct the provider integration. A vague paid flag can hide important differences if several stages are represented by the same field.
Also identify the merchant’s fulfillment decision. The project should state which accepted payment evidence is required before the order may advance, rather than assume that a database update defines a universal commercial policy.
Read the payment-method scope before modeling the stages
Stripe’s separate authorization and capture guide describes holding funds on an eligible payment method and capturing later. It also explains that authorization expires and that supported methods and validity conditions differ.
This is a provider-specific example of separate stages, not a rule that all payment methods use the same sequence or timetable. The actual integration and method need to be identified for the application under evaluation.
Do not copy a generic authorization duration into the database acceptance plan. Preserve the relevant provider evidence and applicable conditions so the application can interpret the particular order correctly.
Keep the states and their authorities distinct
An evaluation record can clarify which event justifies each application change.
| State question | Evidence to establish | Responsible boundary |
|---|---|---|
| Merchant order accepted | Which order and terms does the service recognize? | Merchant application |
| Authorization available | Which provider evidence supports the hold? | Selected payment arrangement |
| Capture outcome | What is known about the capture step? | Provider integration and merchant interpretation |
| Authorization no longer usable | Which applicable condition changed? | Supported provider lifecycle |
| Fulfillment allowed | Which approved business rule is satisfied? | Merchant process owner |
This is an original planning aid. It does not specify a payment contract, financial entitlement, or universal order-state schema.
Compare OceanBase at the merchant record boundary
OceanBase Enterprise is a distributed relational candidate for the merchant’s supported transaction and order-record requirements. The proposal should explain the relationships and accepted updates the application needs to maintain.
CockroachDB provides another distributed relational route. Compare the same merchant-state requirements and identify the implementation work each arrangement needs.
Neither database description independently proves that a payment provider authorized or captured funds. The buyer should evaluate the external integration separately and avoid presenting a committed merchant record as proof that every external payment step completed.
Demonstrate an authorized order before capture
Consider a hypothetical merchant using a supported separate-capture flow. The demonstration should show an order with authorization evidence while capture has not yet completed, then explain the approved application and fulfillment behavior.
Next, show how the service records an accepted capture outcome. Staff should be able to distinguish that result from the earlier authorization without relying on an ambiguous success message.
Include a case where the authorization is no longer usable under the applicable provider arrangement. Ask the team to explain how the application recognizes the condition and which business process decides the next step.
Preserve the order reference, provider association, observed state, and decision evidence. The test should not infer capture merely from a customer notification or another locally generated action. Where information is unresolved, the application needs an approved way to represent that uncertainty.
These are proposed acceptance exercises. No payments were authorized, captured, canceled, refunded, or sent to a provider for this article.
Keep the amount and currency associated with each observed stage. If the actual integration permits another supported capture arrangement, document it explicitly rather than assuming the initial authorized amount and every later merchant record always represent the same financial event.
Maintain the integration contract as payment methods change
New methods and provider configurations can change the lifecycle the application must interpret. Keep the accepted state definitions and authority boundaries with the integration requirements.
OceanBase can be attractive when its supported transactional arrangement serves those merchant records with appropriate operating work. Alternatives should face the same state and evidence requirements.
The practical outcome is an order service that can explain what has been accepted, what the payment provider has established, and why fulfillment may proceed. Authorization and capture can belong to one customer journey while remaining different events that deserve different evidence.
This article is based on documented sources and editorial analysis. Proposed evaluation examples are not independently measured benchmark results.