> For the complete documentation index, see [llms.txt](https://articles.optty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://articles.optty.com/payment-methods-best-practices/how-to-apply-api-credentials.md).

# How to apply API Credentials

## Overview

Every Payment Method provides their Merchant Credentials in slightly differing formats. On this page, we will help you to understand how to add some of these non-standard credentials into the Optty Universal Payment Platform. 

## Grab

### Add Credentials

Grab will provide 5 components for the API credentials. Please follow the format below to add the grab credentials to the Optty Universal Payment Platform. \
Between each of the components, you will need to add a | (Pipe Character) with no spaces before or after it.

**API Key:** Partner ID|Client ID|Merchant\_ID 

**Secret :** Partner Secret|Client Secret

## Billease

To Capture the Billease API credentials, please follow the steps below: 

{% hint style="info" %}
Use 

*shop\_code* as Api Key 

*access\_token* as Api Secret
{% endhint %}

1. Login to Billease merchant portal -> Select Profile -> Select Shops Copy **Shop Code** as **API Key**

![](/files/udeIv4JEWeKrI9HzPMDi)

2\. Select Integration, Click on the **Copy Icon** beside the **Token ID**, copy the API Token as the **API Secret**. 

![](/files/4gK356pzkbzejTFzQZRh)

## ZIP AU

**Add Credentials**

You only require the `private key` to enable the **ZIP AU** whereas the public key would be for the Zip assets. 

Enter the `Private Key` as both **API KEY** and **SECRET** field. 

![](/files/UG5JoaoZMGnUEeDteMfZ)

You can find more information on authentication in our developer documentation [here](https://developers.zip.co/v2/reference/authentication)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://articles.optty.com/payment-methods-best-practices/how-to-apply-api-credentials.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.