Download the PHP package tilta-io/tilta-php-sdk without Composer

Usage

General usage

For every request there is a

• request service (instance of \Tilta\Sdk\Service\Request\AbstractRequest) Knows anything about the request itself (url, method, authorization)
• request model (instance of \Tilta\Sdk\Model\Response\AbstractRequestModel) Knows anything about the parameters of the request, and acts as DTO to submit the data to the request service
• response model (instance of \Tilta\Sdk\Model\Response\AbstractResponseModel) Knows anything about the response data, and acts as DTO to receives the data from the request service Note: in some cases there is not response. Just a true got returned from the RequestService if the request was successful.

Get a \Tilta\Sdk\HttpClient\TiltaClient-instance

Use the \Tilta\Sdk\Util\TiltaClientFactory to get a new instance.

The factory will store the generated TiltaClient-instance in a static variable. So it will not produce a new request, if you request a new TiltaClient-instance.

Provide a boolean as second parameter to define if the request goes against the sandbox or not.

Get an instance of a request service

You can simply create a new instance of the corresponding service.

Example:

You must not provide the TiltaClient via the constructor, but you should set it, before calling execute on the request service.

Example:

Models

Request models: Validation

Every field of a request model (not response models) will be validated automatically, during calling its setter. If you provide a wrong value or in an invalid format, an \Tilta\Sdk\Exception\Validation\InvalidFieldException will be thrown.

You can disable this automatic validation, by calling the method setValidateOnSet on the model:

The model got validate at least by the request service, to make sure that all data has been provided, and you will get no validation exception through the gateway.

Response models

Every response model is set to be read-only.

You can not set any fields on this model. You will get a BadMethodCallException.

Requests

This documentation should not explain the whole usage of each request. It should only show the main information about each request, and the main usage.

Please have a look into the corresponding documentation of each API Request.

GetBuyerAuthTokenRequest

Use this service to generate JWT token for the buyer, so he can use the buyer-onboarding requests.

Usage

GetBuyerDetailsRequest

Use this service to fetch a buyer from the gateway by its external-id (of the merchant)

Usage

GetBuyerListRequest

Use this service to get all buyers. Use limit & offset to navigate through the pages.

Usage

CreateBuyerRequest

Use this service to create a new buyer.

Usage

UpdateBuyerRequest

Use this service to update buyers data.

You must not provide all buyers data, just these data, which you want to update. If you want to update a sub-object ( e.g. contactPersons or businessAddress), you have to provide all data (of the sub-object), to prevent validation issues. This behaviour may change in the future.

Usage

CreateFacilityRequest

Use this service to create a new facility for a buyer.

Usage

GetFacilityRequest

Use this service to get the active facility for a buyer.

Usage

Expected exceptions thrown by service

CreateOrderRequest

Use this service to create a new order for a buyer.

Usage

Expected exceptions thrown by service

GetOrderDetailsRequest

Use this service to fetch order by the external-id.

Usage

Expected exceptions thrown by service

GetOrderListRequest

Use this service to fetch all orders.

Usage

CancelOrderRequest

Use this service to cancel the order (if it hasn't been invoiced yet).

Please note: If the request was successful, an order-object is returned, instead of a boolean!

Usage

Expected exceptions thrown by service

CancelOrderRequest

Use this service to fetch all orders for given buyer.

Usage

Expected exceptions thrown by service

GetPaymentTermsRequest

Use this service to get the payment terms for an order, which would/may be placed.

Usage

Expected exceptions thrown by service

AddOrdersToBuyerRequest

Use this service to add existing orders, which are not processed by Tilta, to the buyer debtor.

Please note: The ExistingOrder-Model is just a subclass of the Order-Model. The difference is, that you can not set the buyerExternalId for the order, because this value has to be set on the request-model (once). So please make sure that you only provide orders, for one single buyer.

Usage

Expected exceptions thrown by service

CreateInvoiceRequest

Use this service to create a new invoice for (multiple) orders.

Please note: In most cases, the invoice_number is the same as the external_id. The invoice_number is the official printed number on the invoice document, while the external_id is the internal identifier of the invoice in your system. You may submit the invoice_number as the external_id as well if you don't want to submit a separate number.

However, please remember that you always have to use the external_id in future requests as reference to the invoice. So if you are using the invoice_number as the external_id, you have to submit the "invoice number" as the external_id.

Usage

Expected exceptions thrown by service

GetInvoiceRequest

Use this service to fetch a single invoice.

Usage

Expected exceptions thrown by service

GetInvoiceRequestModel

Use this service to fetch all invoices. Optional: You can filter by the buyer-id

Usage

Expected exceptions thrown by service

CreateCreditNoteRequest

Use this service to create a new credit note for a buyer

Usage

Expected exceptions thrown by service

CreateSepaMandateRequest

Use this service to list all sepa mandates of a buyer.

Usage

Expected exceptions thrown by service

GetSepaMandateListRequest

Use this service to create a SEPA mandate for the given buyer

Usage

Expected exceptions thrown by service

GetLegalFormsRequest

Use this service to fetch all legal forms, which would be available for given country.

Usage

Expected exceptions thrown by service

Please note: This service will handle automatically the error if the country code is unknown/invalid. It will return empty item-list.

Additional features

Logging

you can enable logging all API Requests. (maybe we will log other things in the future, too).

You just have to give us an instance of \Psr\Log\LoggerInterface. This could be a logger of the popular monolog/monolog package.

Please note, you can only pass a logger of the mentioned interface. If you have a custom logger, you have to implement the interface. Do not forget to install the package psr/log.

Please note: you should not set a debug-logger in production, because this will log all requests (successful and failed). If you only set a ERROR-Handler it will only log all failed requests.

Example: