> For the complete documentation index, see [llms.txt](https://docs.tylt.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tylt.money/introduction/tylt-crossramp-fiat-crypto-solutions/philippines-php/administration.md).

# Administration

The Administration section is intended for approved PSPs, VASPs, and local infrastructure partners that support the operation of Tylt’s Philippines PHP rail.

These partners provide the underlying local payment, disbursement, conversion, settlement, or liquidity infrastructure required to process PHP pay-ins and pay-outs. Tylt uses this infrastructure to make the Philippines PHP rail available to approved merchants through the Tylt platform, API, dashboard, and ledger systems.

Access to the administration APIs is restricted. Only authorized partner-side actors may use these endpoints.

***

### Partner Role

The Philippines PHP rail is operated through a partner-enabled model.

Depending on the agreed configuration, the PSP / VASP partner may support one or more of the following functions:

| Function                  | Description                                                                                    |
| ------------------------- | ---------------------------------------------------------------------------------------------- |
| PHP pay-in collection     | Receiving or processing PHP payments through supported local payment methods.                  |
| PHP pay-out disbursement  | Processing PHP disbursements to end recipients through supported local payment rails.          |
| Fiat-to-crypto conversion | Converting PHP value into USDT or another supported settlement asset, where applicable.        |
| Crypto-to-fiat conversion | Converting USDT or another supported settlement asset into PHP for pay-outs, where applicable. |
| Rate administration       | Setting or updating the PHP/USDT conversion rate used for transaction creation.                |
| Settlement support        | Supporting settlement, reconciliation, and balance confirmation between the partner and Tylt.  |
| Status reporting          | Providing transaction status updates required for merchant-facing reconciliation.              |

The exact responsibilities of each partner depend on the commercial, operational, and regulatory arrangement agreed with Tylt.

***

### Administration APIs

Approved administration actors may be provided access to the following APIs:

| API                   | Description                                                                          |
| --------------------- | ------------------------------------------------------------------------------------ |
| Set PSMD Rate         | Allows the authorized rate actor to set or update the PHP/USDT conversion rate.      |
| Get PSMD Rate History | Allows the authorized rate actor to retrieve historical rate insertions and updates. |

These APIs are restricted and require partner-level authorization. Unauthorized API requests will be rejected.

***

### Authentication

Administration API requests must be authenticated using Tylt-issued API credentials.

Each request must include:

| Header            | Description                                                                               |
| ----------------- | ----------------------------------------------------------------------------------------- |
| `X-TLP-APIKEY`    | API key issued by Tylt to the authorized partner or rate actor.                           |
| `X-TLP-SIGNATURE` | HMAC SHA-256 signature generated using the API secret and the applicable request payload. |

API secrets must be stored securely and must not be exposed in frontend applications, public repositories, shared documents, or unsecured communication channels.

Tylt may revoke or rotate API credentials where required for operational, security, compliance, or contractual reasons.


---

# 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://docs.tylt.money/introduction/tylt-crossramp-fiat-crypto-solutions/philippines-php/administration.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.