ossph.org valid

Paymongo for Node.js

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T11:01:11.632Z. Cached copy · Source on ossph.org

# Paymongo for Node.js

## Paymongo for Node.js

- [Paymongo for Node.js!](https://paymongo.ossph.org/paymongo-for-node.js.md): A lightweight Node.js client for Paymongo API.
- [Quick Start](https://paymongo.ossph.org/quick-start.md)
- [API Reference](https://paymongo.ossph.org/reference/api-reference.md)
- [Links](https://paymongo.ossph.org/reference/api-reference/links.md): A Link resource represents a one-time use link to receive a payment.
- [Payments](https://paymongo.ossph.org/reference/api-reference/payments.md)
- [Payment Intents](https://paymongo.ossph.org/reference/api-reference/payment-intents.md): A \`PaymentIntent\` resource is used to track and handle different states of the payment until it succeeds.
- [Payment Methods](https://paymongo.ossph.org/reference/api-reference/payment-methods.md): A \`PaymentMethod\` resource describes which payment method was used to fulfill a payment. It is used with a \`PaymentIntent\` to collect payments.
- [Refunds](https://paymongo.ossph.org/reference/api-reference/refunds.md): Paymongo Refunds
- [Sources](https://paymongo.ossph.org/reference/api-reference/sources.md): A Source is a resource to generate your customer's payment instrument.
- [Webhooks](https://paymongo.ossph.org/reference/api-reference/webhooks.md): Webhooks
- [Test Cards](https://paymongo.ossph.org/test-cards.md): You can use these test cards to test your implementation.
- [Change Logs](https://paymongo.ossph.org/change-logs.md)
- [FAQs](https://paymongo.ossph.org/faqs.md)


---

# 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
This site has an agentic ask interface you may use to query the documentation dynamically by asking a question.

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

```
GET https://paymongo.ossph.org/index.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.

Machine-readable: GET /v1/resolve?q=ossph.org · GET /v1/domain/ossph.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ossph.org:
1. POST https://agentwebmap.com/v1/sites/ossph.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ossph.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ossph.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ossph.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.