Skip to main content
Azimut SDK
Cash Dispenser
Fujitsu F53
Self-Service Machine Integration Components

Compact Multi Cassette Media Dispenser

Fujitsu F53 cash dispenser integration for kiosk applications. Match the dispenser variant, cassette configuration and banknotes to the supported runtime before deployment.

Cash dispenser
Configuration-specific capacity
Fujitsu F53 — Compact Multi Cassette Media Dispenser

Connect supported cash-dispensing operations through the Azimut SDK.

The current manufacturer reference describes 2 to 6 cassettes, approximately 500 notes per cassette and up to 3,000 notes at the 6-cassette configuration.
Specify installed cassette count, capacity per cassette and the resulting configured total separately.
Confirm banknote dimensions, condition and material against the exact dispenser variant.
Evaluate readiness, denomination selection, dispensing outcomes and fault recovery with the intended configuration.

Integration & JSON API

Integrate the Fujitsu F53 with your platform

The F53 connects over RS232C, and your application does not need to speak that protocol. The SDK drives the serial interface on the kiosk and exposes the dispenser through a JSON API, so an existing platform integrates the F53 the same way it integrates any other device — with an HTTP call.

Two operations carry the core flow. Check that the dispenser is ready before the session reaches the cash step, then request the amount and read the result from the shared response envelope. Readiness, cassette state, and faults are reported in the same response shape rather than in serial status bytes.

See the JSON API and examples in every language
C# / .NETkiosk-local JSON API
using System.Net.Http.Json;
using System.Text.Json;
using System.Text.Json.Serialization;

record ApiEnvelope(
    [property: JsonPropertyName("code")] string Code,
    [property: JsonPropertyName("message")] string? Message,
    [property: JsonPropertyName("data")] JsonElement? Data);

var api = new HttpClient { BaseAddress = new Uri("http://localhost:8080") };

// 1. Confirm the F53 is ready before the cash step starts.
var status = await api.GetFromJsonAsync<ApiEnvelope>(
    "api/hardware/cash-dispenser/check-dispenser");

if (status?.Code != "0000")
    throw new InvalidOperationException($"F53 not ready: {status?.Message}");

// 2. Dispense the requested amount.
var response = await api.PostAsJsonAsync(
    "api/hardware/cash-dispenser/dispense-amount",
    new { amount = "5000" });

var result = await response.Content.ReadFromJsonAsync<ApiEnvelope>();

if (result?.Code != "0000")
    throw new InvalidOperationException($"Dispense failed: {result?.Message}");

Integration questions

No separate .NET package is required. The SDK exposes the F53 through a language-agnostic JSON API, so a .NET application calls it with HttpClient and System.Text.Json. The same endpoints work from Java, Python, or Node.js without changing the integration contract.

The F53 uses an RS232C serial connection. The SDK owns that interface and the device driver; your application talks to the local JSON API over HTTP and never opens the serial port itself.

Yes. The API exposes named operations such as check-dispenser, dispense-amount, purge, and reset, so an existing application adds the F53 by calling those operations and handling the shared status envelope. The kiosk's cash handling logic stays in your application.

The device contract is shared across the dispenser family, so the same calls address the F56 and F510 as well. Swapping the model changes the driver inside the SDK, not the application code.