Onboarding Application UML

Entity that represents main information about onboarding application.

Secondary identifier which can be used to cross-reference records between TidyPay and integrated systems.

Date when billing configuration is done.

Code of the billing configuration assigned to the merchant.

Reference to the entity that represents enumeration of possible billing configuration statuses.

Date of birth of the merchant.

URL used for cancellation.

Descriptor assigned to Convenience Fee payment card transactions associated with the merchant. Shows up on cardholder statements.

Code of the assigned channel.

City of the mailing address.

IP address associated with API call sent by the merchant.

Country code of the mailing address.

Date when the record was created

Descriptor assigned to Convenience Fee direct debit transactions associated with the merchant. Shows up on account holder statements.

Code of the distribution schema associated with the merchant.

Email address used to send any notifications or discuss any processing issues.

Parameter that defines which Extra Features were requested to be configured

ID of the Onboarding Application which was created for the Fee Processor.

Date when Fee Processor for this merchant was configured.

Current status of the Fee Processor configuration process.

ID of the Onboarding Application used as a template for Fee Processor Onboarding Application.

First name of the merchant.

Date when the folder for onboarding had been set up.

Reference to the entity that represents possible creation statuses of the onboarding application.

Identifier of the object used for references; auto-incremented integer value.

Last name of the merchant.

Date when the onboarding application status was updated the last time.

Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

Code of the associated merchant.

Date when the merchant was created.

Reference to the entity that represents enumeration of merchant creation policy values.

Reference to the entity that represents enumeration of statuses assigned to the merchant creation.

Date when merchant fee profile was configured.

Reference to the entity that represents enumeration of possible statuses of the merchant fee configuration.

Identifier of the merchant within the gateway.

Name of the associated merchant.

Profile of the merchant that an application is assigned to.

Secondary identifier of the merchant/merchant account which can be used for cross-referencing records between the gateway and integrated systems.

Type of the merchant (Affiliate, Merchant, etc.).

Request date assigned to the merchant identifier.

Reference to the entity that represents enumeration of possible statuses of the request assigned to the merchant identifier.

Response date assigned to the merchant identifier.

Reference to the entity that represents enumeration of possible statuses of the response assigned to the merchant's identifier.

Policy of how notifications about onboarding process results are delivered to the merchant.

URL used for notifications.

Reference to the entity that represents onboard agreement document.

Reference to the entity that represents information about business.

Identifier of the processor used for onboarding of the merchants associated with a particular reseller. Assigned to the reseller.

Phone number used to discuss any occured processing issues.

Code of the portfolio that this record belongs to.

Code of the processing application configuration.

Code of the onboarding profile assigned within the system.

Type of the associated merchant's profile.

Date of the provider's profile configuration.

Reference to the entity that represents enumeration of statuses that provider profile configuration can obtain.

Code of the reseller that is referred to the selected account.

URL used for returns.

Social security number of the merchant.

State code of the mailing address.

Represents current status of the application.

Street (line 1) of the mailing address.

Street (line 2) of the mailing address.

List of tags, used to control merchant settings during onboarding process.

Time zone set for application.

Name of the user that had submitted the onboarding application.

ZIP (or postal code) of the mailing address.