EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Invoice Payments API

Connect Stripe for a team, check connection status, and create a payment intent for a customer invoice.

Public API v1 has Stripe Connect setup and invoice payment-intent operations under /invoice-payments. It does not have a general /payments collection.

Endpoints

MethodEndpointAccessPurpose
GET/invoice-payments/connect-stripeinvoices.writeGenerate a Stripe Connect authorization URL
GET/invoice-payments/connect-stripe/callbackProvider callbackComplete Stripe authorization
POST/invoice-payments/disconnect-stripeinvoices.writeDeauthorize and clear the team's Stripe connection
GET/invoice-payments/stripe-statusinvoices.readRead connection state and Stripe account ID
POST/invoice-payments/payment-intentInvoice tokenCreate a PaymentIntent for a customer invoice

Connect Stripe

  1. Call GET /invoice-payments/connect-stripe with an invoices.write bearer token.
  2. Send the user to the returned url.
  3. Let Stripe return to the documented callback with its authorization code and state.
  4. Call GET /invoice-payments/stripe-status with invoices.read.
  5. Confirm connected, status, and stripeAccountId before you turn on online payment.

The callback is for Stripe, not a general client operation. Preserve its state value. Do not try to manufacture callback parameters.

Disconnect Stripe

POST /invoice-payments/disconnect-stripe tries provider deauthorization. Then it clears the saved Stripe account fields. If provider deauthorization fails because the account is already disconnected, Eigenn still clears the local fields.

Treat disconnect as a write. Supply an Idempotency-Key when your client can retry after an unknown network outcome.

Create a Payment Intent

POST /invoice-payments/payment-intent is a public customer-payment operation. It authenticates with the invoice token for the customer, not a team bearer token.

curl --request POST \
  --url https://api.eigenn.io/v1/invoice-payments/payment-intent \
  --header "Content-Type: application/json" \
  --data '{
    "token": "invoice-token-from-the-customer-facing-link"
  }'

A successful response contains:

  • amount
  • currency
  • clientSecret
  • stripeAccountId

Use the client secret only in the intended Stripe payment flow. Do not log it or treat it as an Eigenn API credential.

Payment Status

Invoice-level payment status is also available from GET /invoices/payment-status with invoices.read. See Invoices API for pagination and invoice lifecycle operations.

Legacy Endpoint Boundary

Public v1 does not document:

  • GET /payments
  • GET /invoice-payments
  • POST /invoices/{id}/payment-intent

Use the exact endpoints above. Check request models in the OpenAPI explorer.

Related Pages

  • Invoices API
  • Authentication
  • Errors

Forecasts and Stress Tests API

Compute forecasts, save stress-test scenarios, and read runway through the public metrics and reports contract.

Invoices API

List, create, update, summarize, and manage recurring invoices through public API v1.

On this page

EndpointsConnect StripeDisconnect StripeCreate a Payment IntentPayment StatusLegacy Endpoint BoundaryRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesApproval PoliciesAssistant AutomationAssistant Command CenterAssistant Workspace and Saved WorkBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer FieldsCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionFiles and Document VaultFinancial Analytics and ReportsFinancial OverviewInbox and ApprovalsInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewPlanning Data and DimensionsPlanning Models and FormulasPlanning Time and ActualsPlanning UncertaintyPlanning Versions and CollaborationPlanning Views and ExportsReceivablesReceivables AnalyticsReceivables ControlsScenario PlanningSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransaction CodingTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow OutcomesWorkflow PausesWorkflows
OverviewBuild a Driver-Based Planning ModelBuild and Review a ForecastBuild Your First WorkflowCollaborate on a Planning ModelCompare and Share Planning ScenariosConfigure Approval PoliciesConfigure Assistant OperationsConfigure Customer FieldsConfigure Notifications and BrandingConfigure Planning Time and ActualsConfigure Receivables ControlsConnect Planning Data and ActualsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesCreate Your First Planning ModelDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordReview, Restore, and Export a Planning ModelRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Planning Uncertainty AnalysisRun Your First Command Center ReviewSave and Share Assistant WorkSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API
Overview
Overview