Payment processors
Connect Stripe, Xendit, and bank transfer under Integrations → Payments.
Open Settings → Integrations → Payments. You need Manage integrations. Customer types, currency, billing details, and invoice appearance stay under Settings → Apps → CRM.
Each processor shows a Configured badge when it is ready. Stripe and Xendit also show the webhook URLs, events to subscribe, and a link to that dashboard.
Stripe
Paste the publishable key, secret key, and webhook signing secret.
- In Stripe webhooks, add an endpoint.
- Use the Webhook URL on this page (
/api/workspaces/{workspaceId}/webhooks/stripe). - Subscribe to
checkout.session.completed,checkout.session.async_payment_succeeded,invoice.paid(subscription renewals),customer.subscription.updated(keeps member cancellations scheduled in the Stripe dashboard in sync; cancellations from the community Billing tab work without it),customer.subscription.deleted(cancellations),charge.refunded,charge.dispute.created,charge.dispute.funds_withdrawn, andcharge.dispute.closed. A chargeback reverses the payment and removes access when it opens. Optionally addinvoice.payment_failed: it tells the billing owner their renewal failed, in the community bell, as a push notification and by email when billing emails are on (see Community notifications). Without it, a failed Stripe renewal sends no notification. It changes nothing else; access still follows the paid period. Optionally addcheckout.session.expired: it deletes the unused promo coupon of a community checkout nobody finished (without it, that coupon simply stops working about 65 minutes after the checkout started). - Copy the signing secret back into Planeward.
Invoices can take card payments once Stripe is configured. Community checkout uses the same keys when a plan has a Stripe price ID pasted on it.
Community checkout sends promo codes to Stripe as single-use coupons and reads the plan's Stripe price before every checkout, so a restricted key (rk_…) needs Coupons write and Prices read permission as well. See Promo codes on Stripe.
Xendit
In Configure Xendit, paste your Xendit API Key and Webhook callback token (the callback verification token from Xendit). You do not create products or IDs in Xendit, and you do not paste any into Planeward. Community checkout charges the plan price directly:
- One-time plans — a Xendit invoice
- Weekly, monthly, or yearly plans — a Xendit recurring plan (yearly plans renew every 12 months)
Set two callbacks in the Xendit dashboard:
- Invoice paid — the Invoice paid URL on this page (
/api/workspaces/{workspaceId}/webhooks/xendit/invoice-paid), eventinvoice.paid. - Recurring — the Recurring URL on this page (
/api/workspaces/{workspaceId}/webhooks/xendit/recurring), eventsrecurring.cycle.succeeded,recurring.cycle.failed, andrecurring.plan.inactivated.
Planeward checks the x-callback-token header against the token you pasted.
Xendit sends each callback to one URL. If several workspaces share one Xendit account, forward every callback to each workspace's Invoice paid and Recurring URLs. Each workspace records only the invoices and plans its own checkout created and ignores the rest.
Give the API key the Transaction Read permission. Planeward reads each payment's Xendit fee from your transactions. Without it, the fee stays pending with a note on the payment and isn't deducted. Add the permission within 30 days of the payment and the fee is still deducted.
One-time payment methods
For workspaces billing in PHP or IDR, Configure Xendit also lists the payment methods Xendit offers in that currency, such as QRPh, GCash, or cards. Check the ones buyers may use on one-time plans. The Xendit invoice page then shows only those. Leave all unchecked to offer every method active on your Xendit account.
- Check only methods that are activated in your Xendit dashboard. Checkout fails if the invoice asks for a method your account doesn't have.
- This applies to one-time plans only. Weekly, monthly, and yearly plans always use the methods enabled in your Xendit dashboard, because Xendit recurring plans have no method filter.
- If you change the workspace currency, selections that don't exist in the new currency are ignored.
If a renewal fails, Xendit retries daily up to 3 times and emails the customer a payment link. The plan keeps running. The member keeps access until the paid period ends. If the last retry fails after that, the subscription expires; a later successful cycle starts it again.
Processor fees
Planeward reads the fee Stripe or Xendit kept on each payment, with nothing to set up beyond the Xendit Transaction Read permission. Stripe's fee usually shows within a few minutes. Xendit's shows once the payment settles, which can take a few days. The fee comes off the revenue share of the accounts each product picks. See Processor fees.
How a payment finds its checkout
Before sending a buyer to Stripe or Xendit, Planeward saves the community checkout: the plan, the buyer, the checkout link or affiliate code, any promo codes, and the amounts to charge. The processor only gets that checkout's ID as its reference:
| Processor | Field |
|---|---|
| Xendit invoice | external_id |
| Xendit recurring plan | reference_id (each cycle carries the plan's reference_id) |
| Stripe Checkout | checkoutMetadataId in the session and subscription metadata (also shown as client_reference_id) |
When the webhook arrives, Planeward looks the checkout up by that reference in the workspace the webhook URL belongs to, and only for the invoice, plan, or session that checkout created. For Stripe it reads checkoutMetadataId from the metadata; client_reference_id is there for display only, since a payment link URL can set it. That's where the plan, the affiliate credit, the promo, and the expected amount come from, not from anything else on the processor's side. A Stripe or Xendit payment whose reference names no checkout in that workspace is ignored: no payment, contact, or customer is created and no workflow runs. That's what lets several workspaces share one Stripe or Xendit account. Each workspace's endpoint can receive every event, and each records only its own checkouts. Stripe Payment Links made in Stripe aren't recorded either; add those payments by hand or through the API.
Don't change these references in the Stripe or Xendit dashboard. A payment with an edited reference isn't matched to its checkout.
A checkout that's still unpaid after 30 days is removed once Stripe or Xendit confirms it can't be paid anymore: the Stripe session expired, the Xendit invoice expired, or the Xendit recurring plan never charged. A recurring plan the buyer never finished setting up is deactivated first. Checkouts the processor shows as paid are kept for staff to review.
When access ends
Access always follows the paid period end. Planeward checks for ended subscriptions every hour. Manual plans and plans set to cancel expire at the period end. Stripe and Xendit plans that are still renewing expire 72 hours after it, so a late renewal can land first; access still stops at the period end. Losing access doesn't sign a member out; they see Settings only. See Member access journey and the subscription.* events.
Direct bank transfer
Bank name, account, routing/SWIFT, and instructions. Bank transfer is available once an account number or a payment QR code is set. Staff confirm these payments by hand: mark the invoice paid, or approve the checkout receipt.
At checkout the buyer must enter the transfer's reference and upload a receipt (JPEG, PNG, WebP or PDF, up to 10 MB). Staff review both in Commerce → Receipts. When approving, you can change the reference to match your bank statement; leave it blank to keep the buyer's. The approved reference is saved on the receipt and labels the payment.
Payment QR code
Upload a payment QR code (PNG, JPEG, or WebP, up to 5 MB). It shows on the public invoice when they pick bank transfer, and on Community checkout when they pick Upload receipt. They scan it and pay.
Planeward Docs