Skip to main content
POST
Create Mandate with existing Sender Account

Authorizations

Authorization
string
header
required

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

Headers

Idempotency-Key
string
required

A random key provided by the customer, per unique payment. The purpose for the Idempotency key is to allow safe retrying without the operation being performed multiple times.

Body

application/json

request body for creating mandate

mandate_details
object
required
recipient_account
object
required
sender_account
object
required
metadata
object

Response

Success

mandate_details
object
required
mandate_id
string
required

Finverse Mandate ID (ULID)

recipient
object
required
sender
object
required
status
enum<string>
required

Mandate status

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

Timestamp in ISO format (YYYY-MM-DDTHH:MM:SS.SSSZ)

created_at
string<date-time>

Timestamp in ISO format (YYYY-MM-DDTHH:MM:SS.SSSZ)

error
object
fees
object[]
metadata
object

Additional attributes of the mandate in key:value format (e.g. mandate_internal_id: 1234). It supports up to 10 key:value pairs, whereas the key and value supports up to 50 and 1000 characters respectively.

payment_method_id
string

Finverse Payment Method ID (ULID)

recipient_account
object
sender_account
object