Take Any Amount With a Payment Link

How anyone can POST a custom amount to /public-api/payment-links — one-time or recurring — then send the customer the URL that comes back. They pay on Enopsy's hosted Payment App. Money lands in your Stripe.

Integrator guide, document version 1.0.

1. How It Works — One Endpoint, a URL, Then They Pay

You do not create an order first. You ask Enopsy for a checkout link with the amount you want. The customer pays on that URL. Enopsy writes the records after Stripe succeeds.

Endpoint: POST https://backend-billing.enopsy.com/api/v1/public-api/payment-links

sourceType: 4 = custom amount · billingType: 1 = one-time · billingType: 2 = recurring

What you do with the URL

Copy redirectUrl → put it on a button, email, WhatsApp, or QR → customer pays → money lands in your Stripe.

2. Before You Call — Two Things the Request Must Carry

The public API has no bearer token. Enopsy finds your tenant from the browser origin, then finds which storefront from productOrigin.

Also required on the tenant

• Stripe gateway (secret + publishable keys) attached to that project — Enopsy decrypts the publishable key into the checkout page.
• Payment App base URL on the project (redirect.billing_URL, e.g. yourbrand.payment.enopsy.xyz).

Minimal headers

POST /api/v1/public-api/payment-links
Origin: https://app.yourproduct.com
Content-Type: application/json

Switch: one-time vs recurring

3. One-Time — Charge a Custom Amount Once

Use this for deposits, invoices you priced yourself, "pay ₹X now", event tickets — anything that should not renew.

POST /api/v1/public-api/payment-links
{
  "paymentSourceDetails": { "sourceType": 4 },
  "productOrigin": "6512f0aae91…",
  "amount": 2500,
  "currency": { "code": "INR", "symbol": "₹" },
  "billingType": 1,
  "description": "Website setup — Acme Pvt Ltd",
  "additionalInfo": {
    "additionalDescription": "Acme Pvt Ltd · SO-1042"
  }
}

Optional line items

If you send items[], Enopsy uses their totals. If amount is also sent and > 0, amount wins as the charge. If items is empty, one line is synthesised from description + amount.

{
  "items": [
    { "name": "Design", "unitPrice": 1500, "quantity": 1, "totalAmount": 1500 },
    { "name": "Hosting (year)", "unitPrice": 1000, "quantity": 1, "totalAmount": 1000 }
  ],
  "amount": 2500
}

What comes back — copy this URL

{
  "success": true,
  "data": {
    "slug": "paylink-…",
    "status": 1,
    "statusLabel": "active",
    "amount": { "value": 2500, "currency": { "code": "INR" } },
    "totalAmount": 2500,
    "expiresAt": "2026-09-07T12:00:00.000Z",
    "redirectUrl": "https://yourbrand.payment.enopsy.xyz/pay?payload=…"
  }
}

4. Recurring — Charge a Custom Amount, Then Renew It

Same endpoint. Set billingType: 2 and send the interval. There is still no Enopsy plan — you own the amount. After the first successful pay, Enopsy keeps an Order and re-charges the saved card on the schedule.

POST /api/v1/public-api/payment-links
{
  "paymentSourceDetails": { "sourceType": 4 },
  "productOrigin": "6512f0aae91…",
  "amount": 99,
  "currency": { "code": "USD", "symbol": "$" },
  "billingType": 2,
  "description": "Acme Pvt Ltd — monthly retainer",
  "recurringDetails": {
    "billingInterval": 1,
    "recurringAmount": 99,
    "isOnTrial": false,
    "trialPeriod": { "durationInDays": 0 }
  },
  "additionalInfo": {
    "additionalDescription": "Acme Pvt Ltd"
  }
}

recurringDetails

Custom recurring links do not create an Enopsy Subscription document (that is plan-only). Renewals still run off the Order.

5. The URL — What To Do With redirectUrl

The Payment App is already built. Your job is to get the customer onto that URL before it expires.

What the customer sees

1. Opens https://<your>.payment.enopsy.xyz/pay?payload=…
2. Page decrypts the payload: amount, currency, your logo, Stripe publishable key, one-time vs recurring.
3. Enters card (Stripe Elements — card number never hits Enopsy).
4. If the bank wants 3-D Secure, Stripe shows the challenge, then Enopsy confirms.
5. Success page: /payment-success?summaryRef=…

Tiny integration (browser on your domain)

async function chargeCustom({ amount, billingType, interval, description }) {
  const res = await fetch(BILLING + "/public-api/payment-links", {
    method: "POST",
    credentials: "include",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      paymentSourceDetails: { sourceType: 4 },
      productOrigin: PRODUCT_ORIGIN_ID,
      amount,
      currency: { code: "USD", symbol: "$" },
      billingType,                           // 1 or 2
      description,
      ...(billingType === 2 ? {
        recurringDetails: { billingInterval: interval, recurringAmount: amount }
      } : {}),
    }),
  });
  const json = await res.json();
  window.location.href = json.data.redirectUrl;
}

// one-time  → chargeCustom({ amount: 2500, billingType: 1, description: "Setup" })
// monthly   → chargeCustom({ amount: 99, billingType: 2, interval: 1, description: "Retainer" })

6. After They Pay — What Enopsy Writes, and Where the Money Is

Where to look

• Enopsy → Invoices — branded PDF, amount, customer.
• Enopsy → Transactions — Stripe ids, success/fail.
• Enopsy → Orders — only for recurring custom links.
• Stripe Dashboard — the actual money and payouts.

Optional: tell your own backend

If a webhook URL is configured on the project, Enopsy POSTs events such as payment.succeeded after the charge. Delivery is fire-and-forget — a failure on your side does not undo Stripe.

7. Reference — Field List, curl, and Failures

Copy-paste curl (Origin is a header, not JSON)

paymentSourceDetails must be an object { }, never an array [ ]. Open data.redirectUrl from the JSON response.

# one-time — billingType 1
curl -sS -X POST "https://backend-billing.enopsy.com/api/v1/public-api/payment-links" \
  -H "Origin: https://marketxy.com" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentSourceDetails": { "sourceType": 4 },
    "productOrigin": "6a180fcc94ba01d45a468f39",
    "amount": 10,
    "currency": { "code": "USD", "symbol": "$" },
    "billingType": 1,
    "description": "One-time custom test"
  }'

# recurring monthly — billingType 2
curl -sS -X POST "https://backend-billing.enopsy.com/api/v1/public-api/payment-links" \
  -H "Origin: https://marketxy.com" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentSourceDetails": { "sourceType": 4 },
    "productOrigin": "6a180fcc94ba01d45a468f39",
    "amount": 10,
    "currency": { "code": "USD", "symbol": "$" },
    "billingType": 2,
    "description": "Monthly custom test",
    "recurringDetails": { "billingInterval": 1, "recurringAmount": 10 }
  }'

If it fails