MyJackfruit

Help
Browse topics · Payments, shops and subscriptions

Payments, shops and subscriptions

← Back to Can I be told when someone signs up or orders?

Can I connect Stripe, PayPal or Vipps to my app?

Short answer

A published app cannot take payments from its users or load Stripe, PayPal or Vipps; the security rules do not block a plain link out.

Deeper

GilbPlatform today. GilbPlatform has no part that lets your app take card or other payments from its own users, and no chapter of the Developer Guide, GilbPlatform's guide for people who build apps on it, and no help answer shows how to add a payment service to your app. GilbPlatform's own way for an app to use an outside service, a service run on a computer that is not part of GilbPlatform, does not cover this: its example is a service that removes the background from a photo, and whether a payment service can be used this way is not shown. GilbPlatform itself does take payment for its own paid plans, through Stripe: its Pricing page says Payments are handled securely by Stripe. (https://myjackfruit.com/pricing/, read 13 November 2026). That is not a way for your app to take payments. See: What is an outside service, and what does it learn about me?

What is blocked today. An app put live at its own web address, https://<name>.pages.dev, may fetch data only from its own address and from GilbPlatform's own addresses, such as a vault's address, and run only its own scripts (the small programs that make a page do things); it cannot show another site inside its pages, and a form in it can send only to its own address. It has no server code, code that runs on a computer on the internet for your app: publishing refuses a functions folder, because it would run your code on the server. Publishing is also refused when a file looks like a secret key, such as a Stripe secret key. So your published app cannot load a payment service's checkout (the page where a customer pays), hear back from it, or keep its keys (the secret passwords the service gives you) today. The security rules for published sites do not block a plain link in your app that opens the service's own page. If you need more, write to [email protected].

What your AI could do today. Stripe, PayPal and Vipps are payment services: companies that take card or other payments for you, each under your own account with it. The simplest way needs no payment code in your app: the payment service's own payment page. Stripe, for example, says of its Payment Links: "Create a payment link and share it on social media, in emails, or on your website", on a Stripe-hosted page (https://docs.stripe.com/payment-links, read 13 November 2026). Your AI can put such a plain link in your app; the security rules for published sites do not block it. Your app then does not learn by itself who has paid: Stripe says that after a payment you can see it in the payments overview in the Dashboard, Stripe's own pages for you (https://docs.stripe.com/payment-links/post-payment, read 13 November 2026).

PayPal says its subscriptions let you bill customers at regular intervals rather than collect one-time payments (https://developer.paypal.com/docs/subscriptions/, read 13 November 2026). Vipps MobilePay's developer pages speak of an existing Vipps MobilePay business account enabled for online payment (https://developer.vippsmobilepay.com/docs/APIs/recurring-api/, read 13 November 2026). These services change their offers outside our control; read their own pages.

For your app to know by itself that someone has paid, for example to mark an order or a booking as paid, the payment service must tell it. Stripe says it "sends a checkout.session.completed webhook that you can use for fulfillment and reconciliation" (https://docs.stripe.com/payment-links/post-payment, read 13 November 2026). A webhook is a message the service sends to a web address of yours, and receiving it needs a server, a computer on the internet that runs your app's own code even when no one has the app open. A published app has no server code, so this is blocked today; you check the payments yourself in the service's own pages. Write to [email protected] if you need more.

A payment service gives you secret keys, passwords for programs, and a page in a browser cannot keep a secret. Stripe says: Only publishable keys are safe to expose outside your application’s back end, its server part, and "Don’t put keys in source code or configuration files checked into version control" (https://docs.stripe.com/keys, read 13 November 2026). So a secret key never goes into your app's pages or into a vault, the place where a person or a group keeps their records, and publishing refuses a file that looks like a Stripe secret key. The Developer Guide says a private key belongs on a server, and an app put live at https://<name>.pages.dev has no server, so it has no place for another service's key today. If your app needs a service that gives you a key, write to [email protected] before you sign up for that service; the answer Where do I keep the passwords and keys for the services my app uses? says more.

What you must do yourself: open your own account with the payment service, accept its terms and pay its fees. That agreement is between you and the service; GilbPlatform is not part of it. Ask your AI to list what it needs from you, such as which payment page to link to.

Tell Kai-Zen, the planning agent, what you want; it changes the plan, and Agent.Coder, the agent that writes your app's code, builds the change. Whether you want it is your choice. When your app goes live, its name cannot be a payment brand: a name that is a payment brand, such as paypal or stripe, or starts with one and a hyphen, is refused; the answer How do I put my app or website live on the internet? tells more.

Taking money also brings receipts, taxes and refunds: see What about receipts, VAT and taxes? and What happens when a payment fails or someone wants their money back?

If you need payments in your app, write to [email protected].

This answer is written for a computer screen.

Source: GilbPlatform 0fc5a548 workers/publish-ingest/src/checks.ts:21 and :146 (functions, _worker.js, _headers refused: a functions folder would run your code on the server), :30-37 and :158 (key-shaped strings, incl. a Stripe secret key, refused), :165-171 (the site's own headers: Content-Security-Policy default-src 'self'; script-src 'self'; img-src 'self' data: blob: https://*.gilb.com; connect-src 'self' https://*.gilb.com; form-action 'self'; frame-ancestors 'none'); RuleDeployPagesDev. GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): no route takes payments; src/publish/site-name.ts:16-31 (pay, payment, payments, billing reserved; brand names incl. paypal, stripe refused). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no payment, checkout or booking control in src. Standards: Proc_v_i_c_PublishPagesDev (a built static folder is published at https://<name>.pages.dev); Agent.Coder (GilbStack 14a: a browser-only app cannot keep a key secret). Live help page, sentences shared: Where do I keep the passwords and keys for the services my app uses? Stripe, Payment Links, https://docs.stripe.com/payment-links, and After a payment link payment, https://docs.stripe.com/payment-links/post-payment, both read 13 November 2026. Stripe, API keys, https://docs.stripe.com/keys, read 13 November 2026. MyJackfruit, Pricing, https://myjackfruit.com/pricing/ (Payments are handled securely by Stripe.), read 13 November 2026. PayPal, Subscriptions, https://developer.paypal.com/docs/subscriptions/, read 13 November 2026. Vipps MobilePay, Recurring API, https://developer.vippsmobilepay.com/docs/APIs/recurring-api/, read 13 November 2026. Live help pages, sentences shared: Can I make an online shop, or take payments in my app? (no part that takes payments; outside-service route; brand names refused); What is an outside service, and what does it learn about me?; Do my app's users pay anything?; What does my app need to remember, and how do I tell my AI which information to keep? (Kai-Zen changes the plan, Agent.Coder builds the change). How do I put my app or website live on the internet?

Checked against GilbApp d529620.