CRED

CRED is a fintech, not a marketplace: its developer portal covers Container, PPI Wallet and Cards, its doc pages are empty, and no commerce API exists.

CRED, legally Dreamplug Technologies Private Limited, is an Indian members only fintech built around credit card bill payment, with a UPI scanner, credit products, rewards and a curated in app store where premium brands sell to a high credit score audience. For a brand, CRED is a demand channel reached through a partnerships conversation, not a marketplace you can integrate with. CRED does run a developer portal, at developers.cred.club, but it covers fintech integration and not commerce, and as of 2026-09-21 its documentation pages are not actually serving content: every deep link returns the portal landing shell.

At a glance

What it is

CRED's core loop is credit card bill payment: members pay their card bills through the app and earn coins and rewards. Around that sit several products, all visible on its own site: CRED pay, a UPI scanner and credit card checkout with alias UPI IDs and cashback, CRED cash and CRED money, CRED garage for vehicle management, CRED mint for peer lending, and a curated commerce surface inside the app where partner brands sell.

The commerce surface is deliberately closed. CRED describes itself as "a members-only club that enables the trustworthy to make financial progress" and gates membership on credit score. A brand does not sign up to sell on CRED. It is chosen. CRED's own site has no sell, brand, partner, merchant or store page: cred.club/store, /brands and /partners all return HTTP 404, and brands.cred.club and merchant.cred.club do not resolve. The host does return genuine 404s, so those are real absences, not a routing artefact.

CRED pay's marketing describes the brand side only from the member's point of view, as "picking a partner brand outlet, paying with CRED pay, and claiming 2x cashback". That is the relationship: a brand is a partner outlet in a rewards programme, and the commercial terms are the cashback funding split, not a commission schedule.

API access

There is a developer portal, and it is genuinely CRED's: developers.cred.club serves a Docusaurus site titled "CRED Developer Portal", footered "© 2026 Dreamplug Technologies Pvt. Ltd."

What it says it offers:

  • Documentation, described as "Guides for Container, PPI Wallet & Cards".
  • API Reference, Authentication and Webhooks under Shared Concepts.
  • Sandbox, "Test environment with test credentials & data", labelled Preview.
  • Support, "Raise a support ticket with the CRED integrations team and track its status".
  • Error handling, Go-live status and Monitoring, all three labelled "Coming soon".

What it actually serves: nothing. /docs/api, /docs/shared/authentication, /docs/shared/webhooks and /sandbox all return HTTP 200 with a 21,212 byte response that is byte for byte the portal landing page. The documentation pages are routed but not published. The portal's own footer links to https://docs.cred.club/, which does not resolve at all.

Warning

A developer portal whose every documentation route serves the index, with three of its six sections marked "Coming soon" and a broken link to its own docs host, is a portal under construction. Treat CRED as partner gated for now: the route to integration is the support ticket the portal itself points at, not a specification you can read.

The three named products, Container, PPI Wallet and Cards, are fintech primitives. PPI is a prepaid payment instrument under Reserve Bank of India regulation. Cards is card issuing. Container is undefined by anything we could read. None of the three is a commerce API, and none would give you an order, a listing or a stock level.

Authentication

Not published. The portal lists Authentication as a Shared Concept and does not serve the page. No endpoint, header, key, token lifetime or signing scheme can be stated, and none should be guessed.

Objects we can read

None of the unified objects. To be specific about why, rather than just asserting it:

  • Orders. CRED store orders belong to CRED. Nothing in the published product set exposes them to a brand.
  • Listings, products, inventory. The in app catalogue is built by CRED from brand supplied information. There is no catalogue interface.
  • Shipments and returns. Fulfilment arrangements are per partnership. CRED publishes a return policy for members, which confirms physical goods are sold, and publishes nothing about the brand side of a return.
  • Payments and settlements. A brand partner is paid under its partnership agreement. CRED pay, on the merchant side, is a payment acceptance method that reaches merchants through payment aggregators rather than through a direct CRED merchant API that we could document.
  • Customers. CRED's entire proposition is member privacy, including alias UPI IDs that "hide your sensitive details from merchants when you pay". Assume you will never receive member identity.

Writing back: listings, price and stock

Not available. Catalogue, price and offer construction on CRED is a negotiated campaign, run by CRED's team from assets and terms a brand supplies. Plan for a spreadsheet and a calendar, not a connector.

Webhooks and notifications

Advertised in the portal navigation, not documented. Nothing to subscribe to today.

Rate limits and pagination

Not published.

Mapping to the unified model

Nothing maps today. If a partnership gives you reports, the realistic shape is:

Gaps and open questions

  • Whether the CRED developer portal's documentation is access gated to approved partners rather than simply unfinished is unverified. Either way, it is not readable from outside.
  • What "Container" means in CRED's product vocabulary is unverified. It is named in the portal and defined nowhere public.
  • Whether CRED offers any brand facing reporting interface for its in app store is unverified. Nothing public suggests one.
  • Whether CRED pay acceptance is available to merchants directly or only through payment aggregators is unverified from CRED's own sources.
  • No aggregator we could check lists CRED as a channel, including Unicommerce's public integration list.

Sources

  • CRED, homepage and link set, read 2026-09-21. This host returns genuine 404s, so absent paths are real absences
  • CRED pay, for the partner brand outlet model, alias UPI IDs and the cashback proposition
  • CRED Developer Portal, for the product list, section names and "Coming soon" markers. Its /docs/api, /docs/shared/authentication, /docs/shared/webhooks and /sandbox routes all returned the identical landing page on 2026-09-21
  • https://docs.cred.club/, linked from the developer portal footer, does not resolve
  • CRED on Wikipedia, for Dreamplug Technologies and the company background
  • Unicommerce integrations list, which does not name CRED