Volley

Payment requests

Parameter reference for creating payment requests.

Body parameters

FieldRequiredDefaultDescription
bank_account_idYesID of the bank account that will receive funds. Must be verified — list your accounts via the API.
amountYes*Requested amount as a currency string, e.g.
"10.00 NZD".

*Not required for recurring requests, where the amount is governed by recurring_options.
messageYesShort description shown to the customer explaining what they're paying for. Max 180 characters.
typeNosinglesingle for one-off payments, multi for reusable requests. Recurring requests must use single.
referenceNoFree-text reference on the customer's and your bank statement. Max 12 chars, [a-zA-Z0-9-].
merchant_identifierNoFree-text identifier for your own reconciliation. Inherited by all payments from this request.
merchant_customer_identifierNoStable identifier for a known customer in your system (e.g. a hashed user ID). Enables repeat-payment detection.
expires_inNoDuration string (e.g. "10m", "1h") after which the request expires. If omitted, the request never expires.
allow_dynamic_amountNofalseIf true, customers self-select the amount they pay and amount is ignored.
min_payment_amountNo100Minimum dynamic amount in cents. Only relevant when allow_dynamic_amount is true.
max_payment_amountNoMaximum dynamic amount in cents. Required when allow_dynamic_amount is true.
require_customer_basic_infoNofalseRequire the customer to provide email and name before payment.
collect_customer_phoneNofalseAllow the customer to optionally provide their phone number.
require_customer_phoneNofalseRequire a phone number before payment.
require_customer_addressNofalseRequire an address before payment.
success_redirect_urlNoURL to redirect to after successful payment. Host must be configured in Domains settings.
failure_redirect_urlNoURL to redirect to after failed payment. Host must be configured in Domains settings.
recurring_optionsNoRecurring payment limits. See Recurring options.
cust_infoNoCustomer identification. Required for recurring requests, where at minimum an email must be provided. See Customer info.
options.generate_qr_codeNofalseIf true, the response includes a QR code data URL as request.qr_data.

Recurring options

Constraints that limit the type and frequency of payments made after a customer authorises a recurring request.

FieldRequiredDescription
periodYesWindow over which the period limit applies. One of daily, weekly, monthly.
max_per_periodYesMaximum total charge across the period, e.g. "50.00 NZD" for a monthly period means no more than $50/month.
max_per_paymentNoMaximum charge for any single payment. Set this equal to max_per_period for a fixed subscription.
total_countNoCap on the total number of payments across the life of the consent (e.g. 6 instalments).
total_amountNoCap on the total value of all payments across the life of the consent.
end_dateNoDate after which no further payments can be taken.

Customer info

Customer identification details supplied when creating a payment request. Required for recurring requests, where at minimum an email must be provided.

FieldDescription
emailCustomer email address.
first_nameCustomer first name.
last_nameCustomer last name.
phoneCustomer phone number.

On this page