Skip to main content
POST
Update Payment User

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

paymentUserId
string
required

Body

application/json

request body for updating payment user

email
string | null
Maximum string length: 256
metadata
object | null
name
string | null
next_bill_update
string<date-time> | null
user_type
enum<string> | null
Available options:
INDIVIDUAL,
BUSINESS

Response

Success

Flag indicating whether the user has agreed to future (on-demand) payments of bills/invoices owed by the user. This consent is usually collected in the Payment Link flow. Value is false by default, unless: (i) the user enrolled into Autopay in the Payment Link UI, (ii) a Payment LInk was created with the configuration payment_setup_options.future_payments = AUTOPAY, (iii) the Payment User was created with autopay_consent = true using the Create Payment User API (POST /payment_users).

Example:

false

created_at
string<date-time>

Timestamp when the Payment User object was first created

email
string

Payment User's contact email, used for Finverse notifications. To ensure a smooth payment experience for end-users and to avoid support tickets or disputes, we strongly recommend enabling Finverse notifications by providing the end-user's email. Finverse sends email notifications for: - Changes to stored payment methods (e.g. direct debit mandate or card) - Changes to user autopay consent - Executed payments (except card payments via Stripe, since Stripe sends its own notifications). Contact [email protected] for the full list of email notifications sent by Finverse.

external_user_id
string

Customer App's unique ID for the user. This ID is used to identify returning users across user sessions and load the user's previously stored Payment Method and settings. For example, a returning user can: - Directly pay a Payment Link (in mode= payment) using their stored Payment Method, without re-entering payment details. - Use a Payment Link to edit their stored Payment Method. - Use a Payment Link to turn Autopay on/off (by editing their Autopay consent), if allowed by the Customer App.

integration_metadata
object
metadata
object

Customer-supplied attributes in key:value format. E.g. employer_name: Apple Inc

name
string

User's name or nickname (note: this does not need to exactly match the accountholder name of the user's account; however accountholder name inputs may be verified against this value).

next_bill_update
string<date-time> | null

Timestamp when Finverse is scheduled to attempt to fetch the next bill/invoice for this user. Bill/invoice ingestion is one of the available methods for Finverse to initiate Autopay bill collections on each bill due date, using the user's saved payment method(s). Note: bills will only be fetched if the Customer App has configured a 3rd party ERP/CRM or Accounting integration, enabling Finverse to fetch bill/invoice data from the 3rd party source (e.g. Xero, RapidStor). Contact [email protected] to discuss 3rd party bill/invoice integrations and Autopay flows.

updated_at
string<date-time>

Timestamp when the Payment User object was last updated

user_details
object[]

Additional information about the user's identity

user_id
string

Finverse unique ID for the user.

user_type
enum<string>

Type of user (used to determine what user authentication inputs are required, e.g. individual ID vs. company registration details). Possible values: INDIVIDUAL, BUSINESS

Available options:
INDIVIDUAL,
BUSINESS