Please enable JavaScript to view this site.

Mollie Forums

Mollie API Data Model

Navigation: Schema: V2 > Tables

Payments: Mollie Payments

Catalog: Mollie

Schema: V2

Primary Keys: id

Label: Payments

This is a read-only table. The Mollie API may not support changing the data or the Invantive SQL driver for Mollie does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Mollie API.

Table Columns

The columns of the table Payments are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

amount_currency

string

Amount (Currency)

☑

 

amount_value

decimal

Amount (Value)

☑

 

amountRefunded_currency

string

Amount Refunded (Currency)

☐

 

amountRefunded_value

decimal

Amount Refunded (Value)

☐

 

amountRemaining_currency

string

Amount Remaining (Currency)

☐

 

amountRemaining_value

decimal

Amount Remaining (Value)

☐

 

countryCode

string

Country Code

☐

 

createdAt

datetime

Date Created

☑

 

description

string

Description

☐

 

details_consumerAccount

string

Details Consumer Account

☐

 

details_consumerBic

string

Details Consumer BIC

☐

 

details_consumerName

string

Details Consumer Name

☐

 

id

string

ID

☑

 

locale

string

Locale

☐

 

metadata

string

Metadata

☐

 

method

string

Method

☐

 

mode

string

Mode

☑

 

paidAt

datetime

Paid at

☐

 

profileId

string

Profile ID

☐

 

redirectUrl

string

Redirect URL

☐

 

resource

string

Resource

☑

 

sequenceType

string

Sequence Type

☐

 

settlementAmount_currency

string

Settlement Amount (Currency)

☐

 

settlementAmount_value

decimal

Settlement Amount (Value)

☐

 

status

string

Status

☐

 

webhookUrl

string

Webhook (URL)

☐

 

 

16-08-2023 20:15 Version 22.1.262-BETA+4120

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer