Skip to main content

Setting Repayment Terms

Introduction​

Repayment terms define when a buyer must pay. With Two, due dates depend on which flow you use:

  • Standard order invoicing (single-order invoice)
  • Billing Accounts (grouped statements)
  • Instalments (Order API instalment flow)

This guide aligns repayment-term behavior across those flows.

Prerequisites​

1. Standard Orders (Funded Invoices / Net Terms)​

For standard orders, repayment terms are applied at invoice level.

  • The term starts when the order is fulfilled and invoiced.
  • Merchant defaults come from your commercial agreement with Two.
  • For non-billing-account orders, you can set order-level net terms using terms.duration_days in POST /v1/order.

Example (order-level net terms):

{
  "terms": {
    "type": "NET_TERMS",
    "duration_days": 30
  }
}

Related endpoint:

2. Billing Accounts (Grouped Statements)​

For billing accounts, repayment terms are statement-based, not per-invoice net terms.

  • Configure terms at billing account level.
  • Key fields are schedule, due_in_days, and generation_delay_days.
  • start_date and end_date represent period coverage.
  • due_date is the actual payment due date.

Important behavior:

  • Grouped statements are generated snapshots.
  • Grouped statements GET is read-only; it does not create or regenerate statements.
  • Visibility timing follows: period end + generation delay + next generation run.

Example (create billing account):

{
  "primary_email_addresses": [
    "[email protected]"
  ],
  "schedule": "MONTHLY",
  "buyer_company": {
    "country_prefix": "GB",
    "organization_number": "00123456"
  },
  "due_in_days": 30,
  "currency": "GBP",
  "generation_delay_days": 4,
  "account_name": "Example Buyer Monthly Account"
}

Related endpoints:

3. Instalments (Order API)​

Two also supports instalment-style repayment through Order API terms.

  • This is a separate order model from standard net terms.
  • Instalments and billing-account grouped terms should not be mixed for the same order.
  • Available structures depend on your Two configuration.

Example (instalments):

{
  "terms": {
    "type": "INSTALMENTS",
    "number_of_instalments": 12,
    "period": "MONTHLY"
  }
}

Related endpoint:

Term Selection Order (Practical Precedence)​

For each order, use one primary repayment structure.

  1. If terms.type is INSTALMENTS, instalment terms apply.
  2. If billing_account_id is set, billing-account statement terms apply (schedule, due_in_days, generation_delay_days).
  3. If no billing_account_id and no instalments, order-level terms.duration_days (if provided) applies.
  4. If none of the above are provided, merchant default terms apply.

Configuring and Displaying Terms to Buyers​

  • Contract/agreement with Two defines your baseline available terms.
  • Billing-account buyers should see statement-based repayment messaging.
  • Standard-order buyers should see invoice/net-term messaging.
  • Checkout copy should reflect actual behavior (for example, statement due dates vs invoice due dates).
  • Keep due-date wording consistent between checkout, confirmation pages, and PDF documents.

Buyer-Facing Clarity Checklist​

  • Show whether the buyer is on invoice terms, statement terms, or instalments.
  • Avoid presenting statement period dates (start_date/end_date) as due dates.
  • For grouped statements, show or reference due_date.
  • Reinforce terms in order confirmation and invoice/statement communication.

Key Considerations​

  • For standard invoicing, fulfillment/invoice timing drives due-date start.
  • For billing accounts, schedule + delay + generation cadence drives when statements become visible.
  • For amendments (for example refunds), updated statement versions appear after amendment delay + next generation run.
  • Terms remain subject to Two credit and risk policies.

Conclusion​

Repayment-term behavior depends on the selected payment structure. Use net terms for standard orders, statement terms for billing-account flows, and instalments for instalment-specific use cases. Align your checkout wording and support workflows with the model you implement.

For account-specific term setup questions, contact your Two account manager or [email protected].

Legacy: Repay API

Two also offers a separate Repay API for specialized repayment use cases. This typically requires a broader integration scope than standard order flows.