Good morning, Loading account…
Your applications.
Create an application first. Products, payment requests, credentials and code redemption all belong to an application.
Basic details
Tell us what you are connecting to SquashberryPay.
Use Test while integrating and switch to Live when your app is ready for real payments.
Payments waiting for you.
Pick a payment on the left, check the receipt, then confirm or reject.
Every payment, in one place.
Search, filter and inspect recorded payment activity.
Know who is paying you.
Customer records and payment history from your connected applications.
Money recorded by SquashberryPay.
Transparent figures only. Payout balances are shown once a payout rail is connected.
Payouts are not enabled yet
SquashberryPay currently records and verifies merchant payment activity. We will not display a fictional “available balance” or payout amount until a real settlement rail is connected.
Your payment links.
Create, preview, copy and manage hosted checkout links from one place.
Create a secure checkout link
Choose the application and product this link should open.
Who is engaging with your links.
Track visits, unique browsers, payment starts and completed payments for any date range.
Payment methods.
Manage the destinations customers can use to pay your applications.
Add a payment destination
Tell customers exactly where and how to send their payment.
Your products.
Products define what customers can buy, subscribe to or donate toward.
Create a customer offering
Configure pricing, billing and optional donation controls.
API-only variable pricing. Each payment request must include a positive amount. These products cannot be used for fixed-price hosted payment links.
Subscriptions.
Separate recurring products from future subscription activity and billing management.
Subscription activity
Active subscriptions, pauses, cancellations and upcoming renewal reminders will appear here as billing activity is recorded.
Donations.
Campaigns, payment destinations and donation activity stay together here.
Donation payment destination
Configured destinations are shown first. Add a destination only when you need another one.
Where donor payments should be sent
These destinations are used by standalone donation checkout.
Add donation payment method
Add the account or instructions donors should use.
Donation verification
Customer receipts and confirmed donation payments appear in Verify payments and Payments.
Understand your payment business.
Use recorded transactions to see revenue, volume, products and payment health.
Revenue by product
Revenue by application
Build with SquashberryPay.
Keep credentials, webhooks and API activity in one place.
API credentials
Client IDs are visible here. Client secrets are only shown when generated and should never be placed in browser code.
Webhooks
Configure an HTTPS endpoint for your application to receive signed payment.completed events and automatically deliver purchases after verification.
AvailableAPI logs
Request-level logs will show status, latency and request IDs once API event logging is enabled.
Coming onlineDocumentation
Use the integration guide to configure signed payment webhooks for automatic fulfilment after payment confirmation.
Business settings.
Account information and security controls.
Business profile
Session security
Your merchant session is stored in this browser session. Sign out to invalidate the local session.
Payment alerts
Granular notification preferences will be connected to Resend delivery settings.Connect SquashberryPay.
Create an app, define what customers can buy, configure payment destinations, then add the hosted checkout button.
Create an app
Connect a website, web app or mobile application.
Create products
Define one-time, subscription or donation offerings.
Configure payment methods
Add Wave, APS, NADA or bank transfer instructions.
Create a payment link
Generate a hosted checkout that can be shared anywhere.
Deliver verified payments
Configure your HTTPS webhook to receive signed payment.completed events. Customers no longer need to enter a payment code.
Set your application's HTTPS webhook URL in Applications. SquashberryPay sends a signed payment.completed event after a payment is verified and marked complete. Verify X-SquashberryPay-Signature with your application's Webhook Secret against the raw request body and X-SquashberryPay-Timestamp before fulfilling anything. Use X-SquashberryPay-Event-ID for idempotency so retries never deliver the same purchase twice.
{
"type": "payment.completed",
"data": {
"payment_id": "payment-id",
"payment_reference": "SBP-reference",
"external_user_id": "your-user-id",
"product_id": "product-id",
"product_code": "premium_monthly",
"status": "completed",
"payment_state": "completed"
}
}After a valid signature and matching payment are confirmed, grant the product or subscription to external_user_id. Keep your webhook secret on the server; never expose it in browser code.