Install Jentic One Beta

Connect the Billplz Payment API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Billplz Payment API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbillplz.com%2Fbillplz" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbillplz.com%2Fbillplz" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Billplz Payment API.

Create collections to group bills under a single payment page

Issue bills (payment requests) with email or SMS delivery to customers

Look up the live FPX bank list to drive online banking payment selection in checkout

Tokenize cards with POST /v4/cards and charge them later via /v4/bills/{bill_id}/charge

Pre-authorize and later capture card payments using /v4/bills/{bill_id}/preauth and preauth_capture

GET STARTED

Start building with Billplz Payment API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Billplz Payment API for, with concrete tasks.

★ Malaysian E-Commerce Checkout with FPX

Malaysian e-commerce merchants need FPX online banking acceptance alongside cards. The Billplz Payment API creates a bill via POST /v3/bills under a collection, returns a hosted payment URL that supports FPX (with the bank list served by /v3/fpx_banks) and card payments, and notifies the merchant via webhook. Integration is typically two to three days for a first-time merchant.

Create a collection, then create a bill for 99.90 MYR for customer email buyer@example.com with a redirect URL, and return the resulting Billplz payment URL.

Card Tokenization and Recurring Charges

SaaS and subscription businesses need to retain a card for recurring billing. The Billplz API supports tokenization via POST /v4/cards, then charges saved tokens via POST /v4/bills/{bill_id}/charge. Combined with /v4/bills/{bill_id}/preauth and preauth_capture, this covers the standard authorise-now, capture-later flow used in fulfilment-driven businesses. Setup takes around three days including webhook handling.

Create a card token via POST /v4/cards for the customer, then issue a bill and charge that token via POST /v4/bills/{bill_id}/charge for 49.00 MYR.

Outbound Disbursements via Payment Orders

Marketplaces and platforms need to disburse funds to vendors and beneficiaries. Billplz exposes /v5/payment_order_collections and /v5/payment_orders for creating and retrieving outbound payouts, plus /v5/payment_order_limits to check current sending limits before issuing a batch. This is the supported route for splitting funds out of the platform.

Check current limits via GET /v5/payment_order_limits, then create a payment order for 500 MYR to a named beneficiary via POST /v5/payment_orders.

AI Agent Payments Assistant via Jentic

An AI assistant for Malaysian merchants can issue payment links, look up FPX banks, and disburse funds via natural-language requests routed through Jentic. The API Secret Key is held in your Jentic One instance, so the assistant never sees the raw credential. Setup through Jentic is under an hour, versus several days for direct integration.

Search Jentic for 'create a Billplz bill', load the POST /v3/bills schema, and execute it for 199.00 MYR to a named customer's email.

Key Endpoints

37 endpoints — jentic publishes the only available openapi specification for billplz payment api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v3/bills

Create a bill (payment request)

GET

/v3/bills/{bill_id}

Retrieve a bill

POST

/v3/collections

Create a collection

GET

/v3/fpx_banks

List FPX participating banks

POST

/v4/cards

Create a card token

POST

/v4/bills/{bill_id}/charge

Charge a tokenized card

POST

/v4/bills/{bill_id}/preauth

Pre-authorize a card payment

POST

/v5/payment_orders

Create an outbound payment order

POST

/v3/bills

Create a bill (payment request)

GET

/v3/bills/{bill_id}

Retrieve a bill

POST

/v3/collections

Create a collection

GET

/v3/fpx_banks

List FPX participating banks

POST

/v4/cards

Create a card token

POST

/v4/bills/{bill_id}/charge

Charge a tokenized card

POST

/v4/bills/{bill_id}/preauth

Pre-authorize a card payment

POST

/v5/payment_orders

Create an outbound payment order

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Billplz Payment API by hand means sending your API Secret Key as HTTP Basic auth on every call and building each bill, collection, and card path across its v3, v4, and v5 surfaces yourself. Through Jentic you install once, import Billplz from the API Directory, store the secret key once, and your agent calls it.

Permission scoping

Billplz puts the bill id in the URL path (/v3/bills/{bill_id}, /v4/bills/{bill_id}/charge), so a rule can pin your agent to one bill. You choose the operations it may call, so charging a bill or running a pre-authorisation is not included unless you add them.

Credential isolation

Your Billplz API Secret Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Billplz bill' or 'list FPX banks', and Jentic returns the matching Billplz operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Global card and wallet processor without native FPX

Choose Stripe for global card acceptance; choose Billplz when you specifically need FPX online banking and Malaysian-domestic disbursement support.

Alternative

Adyen Checkout

Global checkout service that supports many local payment methods

Choose Adyen if your business already runs on Adyen globally; choose Billplz for a Malaysia-first integration with simpler onboarding.

Alternative

PayPal Payments

Global wallet and card processor

Choose PayPal where buyers prefer the PayPal wallet; choose Billplz for Malaysian FPX-first checkouts.

Complementary

PayPal Payouts

Cross-border payouts service for global beneficiaries

Use PayPal Payouts to disburse to international beneficiaries; use Billplz payment orders for Malaysian-domestic disbursements.

FAQs

Specific to using Billplz Payment API through Jentic.

Why is there no official OpenAPI spec for Billplz Payment API?

Billplz does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Billplz Payment API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Billplz Payment API use?

The Billplz Payment API uses HTTP Basic authentication, with your Billplz API Secret Key as the username and an empty password. When called via Jentic, the secret key is held in your Jentic One instance so the raw Basic credentials never reach the agent's context.

Can I accept FPX online banking payments through the Billplz API?

Yes. Bills created via POST /v3/bills under a collection that has FPX enabled in its payment methods will display the FPX bank picker in the hosted payment page. Use GET /v3/fpx_banks to retrieve the live list of participating banks for your own checkout UI.

What are the rate limits for the Billplz Payment API?

The OpenAPI spec does not declare explicit numeric rate limits. Billplz's standard practice is to throttle abusive callers and return 429 responses when limits are exceeded. The Jentic SDK retries on 429 with back-off so high-volume bill issuance jobs do not have to handle this manually.

How do I tokenize a card and charge it later through Jentic?

Search Jentic for 'tokenize a card on Billplz', which surfaces POST /v4/cards. Load the schema, supply the card details, and execute to receive a card_id. Later, create a bill and call POST /v4/bills/{bill_id}/charge with the card_id. The Python flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Can I use Billplz to disburse money to vendors or beneficiaries?

Yes. The v5 payment-order endpoints handle outbound disbursements: POST /v5/payment_orders creates a payment order, GET /v5/payment_orders/{id} retrieves status, and GET /v5/payment_order_limits returns current sending limits before you issue a batch.

Can I limit what my agent is allowed to do with the Billplz Payment API?

Yes. Jentic One runs on your own infrastructure, and you decide which Billplz operations and credentials the agent may use. Because Billplz puts the bill id in the URL path, such as /v3/bills/{bill_id} and /v4/bills/{bill_id}/charge, your rules can pin the agent to a single bill. You choose the operations it can call, so charging a card or running a pre-authorisation via /v4/bills/{bill_id}/preauth is excluded unless you explicitly allow it.

Billplz Payment API

Name: Billplz Payment API
Brand: Billplz Payment API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticPaymentsPayment Processingbasic37 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Issue Malaysian payment links, accept FPX and card payments, tokenize cards, and create payment orders through the Billplz payment platform.

Use for: I want to issue a Malaysian payment link to a customer, Create a Billplz bill and email it to a customer, List all FPX banks available for online banking payments, Tokenize a card so I can charge the customer later

Not supported: Does not handle invoicing for tax-compliance purposes, full accounting, or non-Malaysian cross-border payouts - use for Malaysian payment collection, tokenization, and domestic disbursement only.

Jentic publishes the only available OpenAPI specification for Billplz Payment API, keeping it validated and agent-ready. The Billplz Payment API is the programmatic interface to the Malaysian payment platform Billplz, exposing v3, v4, and v5 endpoints for collections, bills, FPX bank routing, card tokenization, and payment orders. Merchants use it to issue payment links to customers, accept FPX online banking and card payments, and manage refunds and webhooks. The spec covers 37 endpoints, with authentication by HTTP Basic using the API Secret Key as the username.

Jentic One on Github View OpenAPI Document