> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/bamboraapac.md).

# Bambora Asia-Pacific (decommissioned)

Bambora Asia-Pacific has been decommissioned. The connector no longer processes payments.

{% hint style="danger" %}
**Decommissioned.** Bambora decommissioned its Asia-Pacific platform in September 2025. The Hyperswitch Bambora Asia-Pacific connector can no longer process payments, and you should not configure it for new or existing traffic.
{% endhint %}

### Status

Bambora announced that the Bambora Asia-Pacific platform would be decommissioned as of September 2025; see the notice banner on the [Bambora Asia-Pacific developer site](https://dev-apac.bambora.com/support/guides/getting-help/contact-us). For questions about the decommissioning, Bambora directs merchants to <BamboraAUFAQ@worldline.com>.

The connector is still present in Hyperswitch, but the API hosts it is configured to call no longer exist: requests to the [production endpoint](https://github.com/juspay/hyperswitch/blob/d8b6ebe773690aa37cf249b2992c2358dbd7f438/config/deployments/production.toml#L48) (`www.bambora.co.nz`) and the [sandbox endpoint](https://github.com/juspay/hyperswitch/blob/d8b6ebe773690aa37cf249b2992c2358dbd7f438/config/deployments/sandbox.toml#L48) (`demo.ippayments.com.au`) fail because neither hostname resolves. Payments, captures, refunds, syncs, and mandate setup routed to this connector will fail.

Removing the connector from Hyperswitch is being discussed. This page will be removed when the connector is.

### What to do

* If you have a Bambora Asia-Pacific connector configured, route its traffic to another connector and disable it.
* Do not create new Bambora Asia-Pacific connector accounts.
* The [Bambora](/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/bambora.md) connector is a separate integration that calls a different API ([`api.na.bambora.com`](https://github.com/juspay/hyperswitch/blob/d8b6ebe773690aa37cf249b2992c2358dbd7f438/config/deployments/production.toml#L47)) and is not covered by this notice.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/bamboraapac.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.