Models
Company
Company data required by EFL for customer onboarding.
Namespace and purpose
Imoli\EflLeasingSdk\Model\Customer\Company models company-level customer data: identifiers, contact details, addresses and statements.
It is embedded inside CustomerData and ultimately sent to /Customer/PostCustomerDataForLon.
Class definition
- Namespace:
Imoli\EflLeasingSdk\Model\Customer - Class: final
Company
final class Company
{
public static function builder(string $guid, string $nip): CompanyBuilder;
public function __construct(
string $guid,
string $nip,
array $emails,
array $phones,
array $persons,
array $addresses,
array $statements
);
public function toRequestPayload(): array;
}
Properties
| Name | Type | Required | Description |
|---|---|---|---|
guid | string | Yes | Unique identifier for the company entry in your system. |
nip | string | Yes | Company tax identifier (NIP) required by EFL. |
emails | EmailAddress[] | Yes | List of company e-mail addresses. |
phones | Phone[] | Yes | List of company phone numbers. |
persons | Person[] | Yes | Contact persons associated with the company. |
addresses | Address[] | Yes | Company addresses (e.g. registered office, correspondence). |
statements | CustomerDataStatement[] | Yes | Consents/statements given by the company. |
Methods
| Method | Kind | Return type | Description |
|---|---|---|---|
builder() | static | CompanyBuilder | Returns a fluent builder for constructing Company instances. |
toRequestPayload() | instance | array<string,mixed> | Serialises the company data into the structure expected by EFL. |
toRequestPayload() returns an array with the following shape:
guid,nip– maps to the respective properties,emails,phones,persons,addresses,statements– each element converted via its owntoRequestPayload()method.
Usage in the SDK
- Nested inside
CustomerData. - Built via
Company::builder()in typical flows before callingEflClient::submitCustomerData.