Skip to main content
GET
Get mandate

Authorizations

Authorization
string
header
required

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

Path Parameters

mandateId
string
required

mandate id

Response

Successful

mandate_details
object
required

Details on the mandate

mandate_id
string
required

Finverse Mandate ID for this mandate. Always unique. Creating a mandate with different idempotency keys will result in two mandates with different IDs.

recipient
object
required

Details on the recipient of the payment

sender
object
required

Details on the sender of the payment

status
enum<string>
required

Current status of the mandate. Possible values: AUTHORIZATION_REQUIRED, PROCESSING, READY_TO_SUBMIT, SUBMITTED, SUCCEEDED, CANCELLED, CLOSED, FAILED Note: CLOSED occurs when a draft Mandate is created by a Finverse Payment Link (with status AUTHORIZATION_REQUIRED), and the user then drops-off or creates a new Payment Method or Mandate. In these cases, Finverse closes the draft Mandate in order to associate a new Payment Method / Mandate with the same Payment Link.

Available options:
AUTHORIZATION_REQUIRED,
AUTHORIZING,
PROCESSING,
SUBMITTED,
SUCCEEDED,
FAILED,
REVOKED
updated_at
string<date-time>
required

Timestamp of the last update to the mandate's record

created_at
string<date-time>

Timestamp when the mandate was first created

error
object

Details on why the mandate failed (returned when status = FAILED). Note: this is used to detail any asynchronous e errors occuring after mandate creation; any synchronous errors (e.g. API validation errors) will instead be returned directly during POST /mandates.

fees
object[]

Details on the fee(s) to be charged

metadata
object

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

payment_method_id
string

Finverse Payment Method ID for this mandate, used to create payments using the mandate (see POST /payments). Always unique. Creating a mandate with different idempotency keys will result in two mandates with different IDs.

recipient_account
object

Details on the recipient's account for the payment (i.e. the Customer App's settlement account at Finverse)

sender_account
object

Details on the sender's source institution and account, which is funding the payment