Skip to main content
POST
Mark payment as paid

Authorizations

Authorization
string
header
required

Authentication Method: HTTP Bearer token.

The runtime requires the literal Bearer prefix — a bare token in the Authorization header is rejected with 401 unauthorized.

Header Format: Authorization: Bearer YOUR_API_KEY

Your API key is a JWT. Live keys operate on live data (livemode: true); test keys operate on isolated test data (livemode: false).

Get your key at: app.gigstack.pro/settings?tab=api

Errors: credential failures are answered by the authentication layer with a raw { "message": … } body, not the standardized envelope — 401 for a missing, malformed or expired token, 403 for a revoked key or a plan without API access. See the Unauthorized and AuthForbidden responses.

Path Parameters

id
string
required

Payment id.

Query Parameters

team
string

gigstack Connect: Target team ID for multi-team access.

Requires gigstack Connect enabled on your team and shared billing account.

Also requires the multipleIssuerAccounts feature on your plan. Requests targeting a team other than the one your API key belongs to return 403 without it.

Only API keys can use it: an OAuth access token sent with another team's id is rejected with 403 Team mismatch with OAuth token.

Optional — omit it entirely unless you are acting on another team. It deliberately carries no example value so generated snippets do not emit ?team=undefined; when the parameter is absent, the team is derived from your API key.

Example: ?team=team_xyz789

Body

application/json
payment_form
enum<string>
required

SAT payment form code

Available options:
01,
02,
03,
04,
05,
06,
08,
12,
13,
14,
15,
17,
23,
24,
25,
26,
27,
28,
29,
30,
31,
99
date
number | null

When the payment was received, as a Unix epoch timestamp in milliseconds (13 digits). The handler feeds this value directly to Luxon.fromMillis() and compares it to Luxon.now().toMillis(), so a seconds-precision value is interpreted as a 1970 date rather than rejected. Defaults to now; a future value returns 400.

Example:

1767225600000

send_email
boolean | null

Whether to send email notifications. Overridden by ignore_emails.

Example:

true

ignore_emails
boolean | null

Suppress notification emails. Takes precedence over send_email — the handler resolves ignore_emails ?? (send_email === false).

Example:

false

amount_received
number | null

Cumulative amount received so far, in the payment's currency (not cents — converted internally to match the payment's stored amount). Omit it, or pass the full payment amount, to mark the payment fully succeeded (the default behavior). Pass a value less than the payment amount to record a partial top-up instead: the payment is set to partially_paid with this cumulative amount, which must exceed the amount already received. A value greater than the payment amount is rejected with 400.

Partial funding additionally requires the team's automatePartialPaymentComplements default to be enabled and the payment to already carry a payment_complement automation (i.e. it originated from a PPD invoice flow) — otherwise the request is rejected with 400.

Required range: x >= 0.01
Example:

500

Response

Payment marked as paid successfully. When amount_received was less than the payment amount, the returned payment has status: partially_paid instead of succeeded.

Standardized success envelope emitted by sendSuccessResponse.

success
enum<boolean>
required
Available options:
true
Example:

true

data
object
required

The operation payload.

timestamp
integer<int64>
required

Server time in epoch milliseconds (Luxon.now().toMillis()).

Example:

1767225600000

message
string

Human-readable summary. Present only when the handler supplies one.

Example:

"Operation completed successfully"