Boku

Connect Boku through Hyperswitch.

Boku cannot be set up from the control center. The dashboard keeps its own list of connectors, and Boku is not in it, so Boku does not appear at app.hyperswitch.io in any mode and there is no activation form to fill in. The connector itself exists in the router and is configured for sandbox, so talk to the Hyperswitch team about how to enable it.

Boku is also at alpha integration status, with two gaps worth knowing before you build on it: manual capture is declared but not implemented, and webhooks are not implemented at all.

If you want to use this connector, reach out on the Slack Community first so someone on the Hyperswitch team can tell you where it stands.

Boku reaches mobile wallets across Southeast and East Asia: DANA and GoPay in Indonesia, GCash in the Philippines, KakaoPay in Korea, and MoMo in Vietnam. Each pays in its own local currency, refunds are supported, and a saved wallet cannot be reused for a later payment.

The shared Activate a connector on Hyperswitch guide does not apply here, because it begins by picking a connector in the control center and Boku is not offered there. See Before you start below.

Status and capabilities

Integration status: alpha

Category: alternative payment method

Webhook flows: None declared in code

Payment method	Type	Mandates	Refunds	Capture methods	Countries	Currencies
wallet	DANA	not supported	supported	automatic, manual, sequential automatic	IDN	IDR
wallet	GCash	not supported	supported	automatic, manual, sequential automatic	PHL	PHP
wallet	GoPay	not supported	supported	automatic, manual, sequential automatic	IDN	IDR
wallet	KakaoPay	not supported	supported	automatic, manual, sequential automatic	KOR	KRW
wallet	MoMo	not supported	supported	automatic, manual, sequential automatic	VNM	VND

The feature matrix declares manual capture, but the capture flow is not implemented: get_url() and get_request_body() both return NotImplemented, and build_request() calls them, so a capture request fails before it is sent. Use automatic capture. Tracked upstream as issue 14372.

Authentication

Boku authenticates with two credentials, named API KEY and MERCHANT ID in the connector configuration. Those are the only two: BokuAuthType::try_from() accepts a BodyKey pair and rejects every other shape. Hyperswitch signs each request from them in build_headers(), so you do not assemble a signature yourself.

The connector configuration carries a third field, Source verification key, which is not a credential: it sits under webhook details rather than connector authentication, and because Boku webhooks are not implemented, it has no effect. Nothing needs to be supplied for it.

Before you start

Boku is not offered in the control center, so the usual activation flow does not apply. Work through the Hyperswitch team instead, and have the following ready.

1. Your Boku API KEY and MERCHANT ID. Those are the only two credentials the connector authenticates with.

2. The wallets your Boku account covers, from DANA, GCash, GoPay, KakaoPay and MoMo.

3. Automatic capture. Manual capture is declared in the matrix but not implemented, so do not plan around it.

You will not be asked for a source verification key. It is a webhook field, and Boku webhooks are not implemented.

Webhooks

Boku webhooks are not supported, so there is no event list and nothing to configure. Use payment sync and refund sync for status updates.

All three incoming-webhook handlers return WebhooksNotImplemented: get_webhook_object_reference_id(), get_webhook_event_type(), and get_webhook_resource_object().

Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7. See Boku connector source and Boku transformers.