Payment Links API

Payment links use merchant payment sessions and should be created with a merchant reference, expiry, optional amount rules, and callback metadata.

Current Surface

  • Use the payment-session endpoint with merchant metadata that marks the flow as a reusable or fixed-amount link.
  • Store the merchant reference and verify every payment using the signed verify endpoint or webhook confirmation.

Endpoints

Endpoint Method Auth Headers Notes
Create payment-link session
/business/api/v1/public/payment-sessions/
Create a payment session that is rendered as a payment link or hosted checkout link.
POST Merchant HMAC
Authenticated caller
X-EGACARD-API-KEY: <merchant-public-key>
X-EGACARD-SIGNATURE: <hmac-signature>
X-EGACARD-TIMESTAMP: <unix-timestamp>
X-EGACARD-IDEMPOTENCY-KEY: <unique-request-key>
Sandbox: Supported with sandbox keys and adapters.
Production: Available subject to verification, country activation, and provider support.
Rate limits: Standard authenticated rate limits