PayIn / Developers

Connect the payment.
Continue the business.

For order-linked checkout, registration updates, or service access, connect payment results to your own system.

Checkout and payment status

The application exposes checkout creation and payment status endpoints. Use a payment identifier to connect a checkout to the record in your own business system.

Ordinary reusable payment links do not automatically establish that order relationship.

Open API documentation

Completion webhooks

The current source sends payment.completed when a callback URL is configured for a link and settlement reports success with a transaction hash.

Payload fields include paymentId, linkId, txHash, amount, currency, network, recipientAddress, payerAddress, and timestamp. A configured callback secret enables an HMAC-SHA256 signature.

This is an existing code path, not a verified delivery guarantee. Durable retries and production delivery reliability have not been established by this website work.

What your integration owns

  1. Associate the payment with the correct order, registration, or customer record.
  2. Verify the event and payment status before performing a business action.
  3. Handle repeated requests, missed delivery, delayed results, and recovery in your own system.
  4. Test the full flow before turning on automatic fulfillment or access.

A webhook alone is not a ticketing, stock, entitlement, or shipping system.

Open and experiments

PayIn Open is an independent self-hosted gateway. You deploy, configure, and operate it. Agent experiments are separate from this checkout integration; no ready-to-use AI Skill is offered here.

PayIn Open on GitHubDeveloper experiments