From a development perspective, the only difference between the data to create a Classic Account and a Transparent Account is the transparentAccount
attribute.
If the Marketplace wants to offer Transparent Accounts to its sellers, this means that the entire settlement and withdrawal process must be shipped on the Marketplace or Platform (done via API). In the case of Transparent Accounts, sellers do not have access to the Wirecard Account with the entire control dashboard.
ATTENTION
The Marketplace has full responsibility for these accounts and for providing service to sellers. No direct contact between Marketplace or Platform vendors and Wirecard can be made in this case.
Name | Description | Details |
---|---|---|
| Attribute to create a transparent Wirecard account. | boolean, |
| Account email. | structured |
└─ | Account email address. It will be used as a login. | string, |
| Personal data. If the registration is for a legal entity, the data must be from one of the partners or attorneys. | structured |
├─ | Name. | string, |
├─ | Surname. | string, |
├─ | Identity Document. | structured |
├─├─ | Document type. Possible value: | string, |
├─└─ | Document number. | string, |
├─ | Identification document. | structured |
├─├─ | Document type. Possible value: | string |
├─├─ | Document number. | string |
├─├─ | Document issuer. | string |
├─└─ | Document issue date. Format YYYY-MM-DD. | date |
├─ | Birthdate. | date (YYYY-MM-DD) mandatory |
├─ | Birth country. 3 letter abbreviation. Example: | string |
├─ | Birth city. | string |
├─ | Affiliation. | structured |
├─├─ | Mother name. | string |
├─└─ | Father name. | string |
├─ | Phone. | structured |
├─├─ | Phone DDI (International code). Possible value: | string, |
├─├─ | Phone DDD (local code). | string, |
├─└─ | Phone number. | string, |
├─ | Alternative phones. | structured list |
├─├─ | Phone DDI (International code). Possible value: | string |
├─├─ | Phone DDD (local code). | string |
├─└─ | Phone number. | string. |
├─ | Address. | structured |
├─├─ | Street name. | string, |
├─├─ | Number. | integer |
├─├─ | Complement. | string |
├─├─ | District. | string, |
├─├─ | Zipcode. | string, |
├─├─ | City. | string, |
├─├─ | State. 2 letter abbreviation. | string, |
└─└─ | Birth country. 3 letter abbreviation. Example: | string, |
| Company data. Used for business accounts only. | structured, |
├─ | Company name. | string |
├─ | Corporate name. | string |
├─ | Company identity document. | structured |
├─├─ | Document type. Possible value: | string |
├─└─ | Document number. | string |
├─ | Main activity branch. | structured |
├─├─ | CNAE activity code. Example: 82.91-1/00. | string |
├─└─ | Activity description. Example: Collection activities and registration information. | string |
├─ | Opening date. Format YYYY-MM-DD. | date |
├─ | Company phone. | structured |
├─├─ | Phone DDI (International code). Possible value: | string |
├─├─ | Phone DDD (local code). | string |
├─└─ | Phone number. | string |
├─ | Address. | structured |
├─├─ | Street name. | string |
├─├─ | Number. | string |
├─├─ | Complement. | string |
├─├─ | District. | string |
├─├─ | Zipcode. | string |
├─├─ | City. | string |
├─├─ | State. 2 letter abbreviation. | string |
└─└─ | Birth country. 3 letter abbreviation. Example: | string |
| Business category. | structured |
└─ | Category identifier, according to the list of categories. See here for possible values. | string |
| Website address. | string |
| Account type. Possible values: | string, |
| Use terms acceptance data. | structured |
├─ | Use terms acceptance date. | datetime |
├─ | User IP address when accepting the terms of use. | string |
└─ | The userAgent used by the user when accepting the use terms. | string |