Skip to content

Create a Project

A project is what an API key, a payment link, or a transaction belongs to — you need at least one before you can integrate anything. Projects don’t require Business Verification to use in sandbox; that’s only needed before a project can go to production.

Go to Proyek (Projects) in the dashboard sidebar and click New project.

The Create project dialog, with fields for project name, category, description, website, and logo

Only the name is required — sandbox is available immediately, and everything else can be filled in later.

Field Required Notes
Project name Yes Up to 120 characters
Category No Food & Beverage, Retail & E-commerce, Services, Digital & SaaS, Education, Healthcare, Donation & Nonprofit, or Other
Description No Up to 1000 characters — describes the business and what the project sells
Website No Your business’s URL
Logo No PNG, JPEG, or WebP, up to 2MB

Creating a project takes you straight to its page, with five tabs: Settings, API Key, Payment links, Payment channels, and Notifications. Category, description, website, and the rest stay editable from Settings afterward — see Project Settings for what’s there, including the production readiness checklist.

From the API Key tab:

The API key creation dialog, showing a newly created sandbox key that starts with sk_test_

Name the key (for your own reference) and create it. The secret is shown once — copy it immediately. This key only works for this project and the environment (sandbox or production) it was created in — see Authentication for how to use it.

From the Payment channels tab, toggle which methods (QRIS and individual VA banks) this project accepts:

The Payment channels tab, listing QRIS and virtual account banks with their fees, each with an on/off toggle

These become the project’s default allowed_payment_methods — the set a payment link or direct payment falls back to when you don’t specify methods explicitly. See Payment Methods for what each method and fee means.