STRIPE integration

[redline]

Hi Team,

I don’t have any technical issue to report here, but I have emailed a couple of questions regarding integrations with Stripe / card / agents. I didn’t use the forum as your list of questions did not match my issues.

Appreciate an answer when you catch a break.

Thank you.

[dongqtm]

Hi redline,

Would you mind telling us more about your project and your plans for the Stripe/card/agents integration? We’d love to learn more about it!

[redline]

Hi Manifold team,

I did send two email with no response.

We’re building for non-crypto collectors who want to pay with credit card, Apple Pay, and Google Pay, often without installing a wallet first.

What we need to break down crypto barrier for our audience of collectors:

A buyer journey that is card-first on our vercel domain, then receives the NFT through a Manifold-aligned mint/claim experience (hosted claim / Studio flows), rather than a parallel “off-books” fulfillment—unless that’s the only supported model for sovereign/imported contracts.

What we already have
We are integrated with Stripe (Checkout + server-side confirmation) and plan to use Stripe as the primary card rails. We can provide whatever technical artifacts help you evaluate partnership or product direction (e.g. Checkout session flow, webhook handler outline, idempotency + fulfillment mapping, screenshots).

Questions (short)

1. For imported/s sovereign contracts, does Manifold support or plan to support a hosted claim/mint path that can be unlocked after off-Manifold payment (Stripe), via voucher / signed payload / allowlist / admin API—or should we assume Stripe payment implies we fulfill on-chain outside hosted claim?
2. Historically, Manifold offered in-product card checkout. If you reimplement in-Studio / in-product card pay, could it route processing to Stripe (or otherwise interoperate with merchant Stripe), and is there anything we can supply from our Stripe integration (schemas, Connect model preference, compliance pack) that would accelerate evaluation?
3. Policy / UX minimums: any required buyer disclosures for “pay on CarCulture (Stripe) → receive Manifold edition”?

We’re happy to a sanitized example Stripe webhook payload + our fulfillment state machine if useful.

Goal: Walletless buyers → Stripe (card / Apple Pay / Google Pay) → your server POST

/api/stripe/webhook → fulfillment aligned with Manifold mint/claim (pattern TBD

with Manifold — hosted claim vs API vs voucher)

See attached pngs.

Thanks,
Cindy

[redline]

Can you answer me please. I have submitted three separate requests–will you accept STRIPE LINK credit cards? Or any credit cards? My customers do not have crypto wallets

[dongqtm]

Hi,

Sorry for the late response. We don’t currently have a direct integration with Stripe. However, we could enable Crossmint integration, which allows credit card payments on your Edition Page. Is this something you might be interested in?

The requirements are:

• You need to use our Edition Page product
• The drop needs to be priced in ETH
• No allowlist

Could you tell me more about your specific drop? What are you selling, what is the pricing structure, who is the target audience, and which network are you planning to use?

[redline]

Thanks for getting back to us.

We’ve already read Manifold’s November 14, 2025 announcement that new Edition Pages can no longer be configured with Crossmint for card checkout in Studio, while existing Crossmint-connected pages continue. Your suggestion to enable Crossmint on an Edition Page may be a partner exception — can you confirm? Perhaps your agent AI lacks this context.

Separately, we wrote a complete integration for Crossmint. They wrote us and indicated our project may not qualify under their current commercial tier, so we need a path that does not assume Crossmint is available. I provided you with Crossmint email.

Our customers need credit card checkout. Unless you intervene with Crossmint, there is No Crossmint, and No STRIPE. Our ask (see the May 2 Stripe appendix we sent) is different: we run Stripe Checkout on our domain (checkout.session.completed, verified webhooks) for sovereign/imported contracts on Base and Ethereum. We need the supported Manifold pattern to convert verified off-platform payment into mint or claim eligibility — including whether allowlist drops are supported.

Edition Page + ETH-only + no allowlist does not match our Route 66,66 drop (fiat-first collectors, allowlist lane).

Can you point us to documentation or an integration owner for: (a) post-Stripe fulfillment on imported contracts, or (b) confirmation that only hosted Manifold checkout (wallet/ETH) is supported and we should mint/transfer via Client SDK / admin minter after payment on our site?

[dongqtm]

Hi Redline,

Sorry for the confusion. We currently do not support direct Stripe integration.

At the moment, the only option is to go through Crossmint, but it seems Crossmint is also limiting support for this feature.

We will continue looking for a solution on our side and will update you if anything becomes available. However, there is currently no available credit card payment solution on Manifold at this moment.

Our apologies for not getting the answer to you sooner,

[redline]

We built our drops as Manifold Edition pages, but with no credit card checkout on Manifold, most of customers are blocked.

We’d like to move primary sales to OpenSea (card-friendly) while keeping our existing contracts and tokens unchanged. Can Manifold disable or remove our Edition pages and advise the supported steps so we can list on OpenSea without breaking existing minters? What is the recommended procedure?

[dongqtm]

Hello Redline,
Sorry that the answer was not what you hope for.
Would you mind sharing the existing contracts and Edition Page link please?
I can take a look to see what your set up was and advise accordingly.

Thank you!