Introduction

AletaPlanet gives you the infrastructure to issue payment cards and manage the money behind them without having to run a bank yourself.

What the platform does

You build the product and bring the customers. We handle the parts behind the scenes: the card program, accounts that hold customer funds, cards issued against those accounts, and the real-time authorization flow that decides whether a payment is approved.

The API gives you:

• Cardholders — the people your cards belong to.
• Accounts — where customer funds are held.
• Cards — virtual cards that can be used within seconds, or physical cards that are personalized and shipped.
• Spend controls — rules and limits that are checked before an authorization is approved.
• Authorizations and transactions — the payment lifecycle, from the merchant's initial request through clearing and settlement.
• Webhooks — state changes sent to you asynchronously, with signatures and replay support.

Read core concepts before you start building. It explains how these objects fit together, and the rest of the documentation builds on that model.

Who it is for

These docs are written for engineers integrating AletaPlanet into their products. You should be comfortable working with HTTP and JSON, but you don't need prior experience with card issuing.

When a payments concept comes up — such as clearing, settlement, holds, or force posts — we'll explain it as part of the relevant API flow.

Most teams use the platform in one of these ways:

You are building	What that looks like here
A consumer wallet or neobank	One cardholder per user, with one account and one or more cards
A B2B spend platform	One cardholder per employee, with cards that can be issued, frozen, and controlled as needed
A marketplace or payout platform	Accounts funded for each payout cycle, with cards used to spend from those balances

What makes this API different

Banking APIs can sometimes expose a lot of the underlying banking infrastructure: teller IDs, branch codes, split date fields, or numeric response codes that don't match the HTTP status.

You don't need to deal with that here.

Instead:

• Identifiers are opaque and typed. The prefix tells you what kind of object you're working with, without exposing our internal systems.
• Errors use one consistent shape. You can build your error handling once and use it across endpoints.
• Money is always an object. Each amount includes its currency and scale, so your code never has to guess what a number means. Financial amounts are never represented as floating-point values.
• Timestamps use one format. You don't have to deal with different timestamp formats or local timezone conversions between endpoints.
• Booleans and enums are readable. You won't find "Y" / "N" flags or numeric codes that require a separate lookup table.

The exact formats are covered in API conventions.

What the platform does not do

There are a few important boundaries to understand when designing your integration.

• Authorization decisions are handled by us. Every approve or decline goes through our decisioning path, which checks the card state, spend controls, and available balance. Passing authorization decisions to your own service is planned, but isn't available today. See real-time decisioning for the current model.
• Identity verification is usually handled by you. For most programs, you verify the cardholder and send us an attestation of the result. Identity documents don't pass through this API. The exact ownership of the verification decision is agreed during program setup. See cardholders and KYC.
• Programs are configured during onboarding. BIN ranges, card products, and fee schedules aren't self-service. We configure these with you during onboarding, and the API provides access to the resulting configuration.

Aleta Planet

Aleta Planet is a Singapore-headquartered payments company, a Visa Principal Member, and a BIN sponsor.

This allows us to support card programs directly rather than requiring another intermediary for the issuing relationship. It also means your program is configured with you during onboarding instead of being limited to a fixed, self-service setup.