Docs

Create Payment

Creates a new payment in Avaza.

POST

Query

Field selectionChoose which fields should be included in the response. Learn more
string

Comma-separated response fields to include.

Body

Arguments
number
string

Optional. If not specified will be automatically generated

date

Date of Payment. If not specified, assumes today.

string

Optional to override the default prefix added to Payment Numbers

number

Only required if no invoice allocations specified.

number

Optional. Only used when the Customer's currecy is different from the Avaza account's base currency. Specifies the exchange rate that should apply between the customer currency and base currency. If not provided we will obtain an up to date exchange rate for the Payment Issue Date.

string

Optional for storing the reference # of the payment method.

string
string

Optional for storing the payment provider who was the source of funds.

objectrequired

List of amounts within this payment that are allocated to invoices. The sum of these be less than or equal to the payment amount.

number

The Avaza Invoice TransactionID that is having a payment amount allocated to it.

number

The Amount being allocated to the invoice. Expects same currency as invoice currency

date

Optional. Defaults to the current time in the Avaza account's timezone. The date the allocation is applied to the invoice. Can be difference from the Payment Date when doing prepayments etc.

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is
One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.
Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.
Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.