Xendit collects payments for 9Pic Checkout across several Southeast Asian currencies. Add one Xendit configuration for your organisation, then assign it to the event that will sell packages.You need a secret key from the Xendit Dashboard. Xendit issues a development secret key while you test and a separate production secret key for real payments.
9Pic does not automatically detect whether a Xendit secret key is a development or production key. Double-check which key you are pasting in before you publish an event for real buyers.
You need permission to view the API Keys page in the Xendit Dashboard.
Correct key for the environment
Use a development secret key for setup checks and a production secret key for public checkout. 9Pic does not block a development key from being used in production, so confirm the key yourself.
A team admin account
Only team admins can open and manage Payment Configuration.
An Enterprise organisation
Payment Configuration and 9Pic Checkout are available on the Enterprise plan.
Supported currencies
Events that use Xendit can only sell packages priced in IDR, PHP, MYR, THB, or VND.
Do not share the secret key in email, chat, task tickets, screenshots, frontend code, or a public repository. If you think it has been exposed, create a new key in Xendit and update the configuration in 9Pic.
Sign in to the Xendit Dashboard and open the API Keys page.
2
Copy the secret key for the mode you need
Copy the secret key for the environment you are working in. Xendit’s own convention starts development keys with xnd_development_ and production keys with xnd_production_.
3
Store the key safely
Keep the key in your organisation’s approved password manager until you add it to 9Pic. Do not paste it into a buyer-facing website or app.
Need help finding the keys in Xendit? Check the Xendit Dashboard’s API Keys page directly, or contact the Xendit team that provisioned your merchant account.
Open the event, then open its Checkout configuration.
2
Assign the Xendit configuration
In the Payment gateway card, select Assign (or Edit if a gateway is already assigned), choose the Xendit configuration, and save.
3
Set package prices in a supported currency
Create or update Checkout packages in IDR, PHP, MYR, THB, or VND. Other currencies cannot be used with Xendit.
4
Publish and test
Publish the packages and run a complete buyer journey with a development-key configuration before you switch the event to a production key.
Xendit does not offer a Pass on fees option in 9Pic Checkout. The listed package price is always the amount charged.
Replacing the assigned gateway while Checkout is live pauses Checkout first. Confirm the new configuration and package currency before you publish it again.
9Pic says the Xendit secret key is not configured.
Edit the Xendit configuration in Payment Config and confirm that Xendit Secret Key has a value. Then assign that configuration on the event’s Payment gateway card.
A development key was used for a public event and I want to prevent that.
9Pic does not block a development secret key from being used in production for Xendit. Review the configuration’s key before publishing packages for a public event, and replace it with a production key when you are ready to accept real payments.
I cannot select my currency, or another currency is blocked.
Events assigned to Xendit can only sell IDR, PHP, MYR, THB, or VND packages. Choose one of those currencies, or assign a gateway that supports the currency you need.
The buyer does not see the payment method I expected.
9Pic does not send a fixed list of payment methods to Xendit. The buyer sees whatever payment methods are enabled on your Xendit account. Enable the method in Xendit, then retry a test purchase.
I expected a Pass on fees option like PayMongo has.
Xendit does not support passing provider fees on to buyers in 9Pic Checkout. The listed package price is always the amount charged.