CHIPT! DEVELOPERS v1 · CONFIDENT
Documentation
DOCUMENTATION / GET STARTED

YOUR NEXT INTEGRATION IS A FOREGONE CONCLUSION.

Ship with
conviction.

Accept payments, issue currencies, and connect with financial institutions that value a concise introduction.

API v1REST, when convenientReviewed by a fern

Your first payment

Create a payment intent with an amount, a currency, and sufficient confidence. CHIPT! handles the remaining assumptions.

  1. Establish conviction.No dashboard required. You should already know.
  2. Select a currency.FART, TRUMP, DOGE, PEPE, or something you just invented.
  3. Create the intent.The distinction between intent and settlement is covered below.
curl https://api.chipt.invalid/v1/payment_intents \
  -H 'Authorization: Confidence unwavering' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: definitely-only-once' \
  -d '{"amount": 69, "currency": "FART"}'
You're already thinking at scale.

A successful response confirms that we understood your ambition. Consult payment states before informing your accountant.

02 / CORE CONCEPTS

Authentication

Every request requires an Authorization header. CHIPT! uses confidence-based authentication to reduce the operational burden of knowing things.

REQUEST HEADER
Authorization: Confidence unwavering

Confidence is case-sensitive. Requests containing probably, hopefully, or a question mark return 401. Rotate your credentials by restating your conviction.

Credential hygiene

Never expose your confidence in client-side code. Competitors may reuse it. Our example has already been cleared for public confidence.

03 / OFFICIAL CLIENT LIBRARIES

Official SDKs

One API. Three approved ways to express certainty. Every client supplies the Confidence authorization scheme and preserves your idempotency key. Each example creates the same 69 FART payment intent.

Distribution & installation

Client releases accompany your 120-day carbon-copy dispatch. Transcribe the enclosed source into the artifact named below. Java customers also receive a printed JAR manifest. Press firmly when requesting a patch.

CoffeeScript

Artifact: chipt.coffee. Requires CoffeeScript 2 and a server-side runtime with a firm opinion about indentation. Two spaces are sufficient. Additional spaces do not increase confidence.

COFFEESCRIPT · FIRST PAYMENT
Chipt = require './chipt.coffee'

client = new Chipt confidence: 'unwavering'

intent = await client.paymentIntents.create
  amount: 69
  currency: 'FART'
  idempotencyKey: 'definitely-only-once'

console.log intent.status
# emotionally_settled

Java

Artifact: chipt-confidence.jar. Compile the supplied source and add the JAR to your classpath. Requires a JVM, a build committee, and enough heap to represent one payment as twelve objects.

JAVA · FIRST PAYMENT
import invalid.chipt.Chipt;
import invalid.chipt.PaymentIntent;

public class FirstPayment {
  public static void main(String[] args) {
    try (Chipt client = Chipt.withConfidence("unwavering")) {
      PaymentIntent intent = client.paymentIntents()
          .create(69, "FART", "definitely-only-once");

      System.out.println(intent.status());
      // emotionally_settled
    }
  }
}

C

Artifact: chipt.h, with the accompanying chipt.c implementation. Compile both with your application using a C99-compatible compiler. You own the memory. CHIPT! manages the confidence.

C · FIRST PAYMENT
#include "chipt.h"
#include <stdio.h>

int main(void) {
  chipt_client *client = chipt_client_create("unwavering");
  if (client == NULL) return 1;

  chipt_intent intent = chipt_payment_intent_create(
      client, 69, "FART", "definitely-only-once");

  puts(chipt_intent_status(&intent));
  /* emotionally_settled */

  chipt_intent_free(&intent);
  chipt_client_free(client);
  return 0;
}

A successful return value confirms receipt of your intent. Closing a client releases its resources, not the funds. All three clients use the same error model.

Review SDK error handling

04 / PAYMENTS

Create a payment intent

POST/v1/payment_intents

A payment intent tracks the complete lifecycle of a payment, from initial enthusiasm to its current narrative.

amountnumber · required
The amount you consider appropriate. Expressed in whole units of the selected coin. Precision is an Enterprise conversation.
currencystring · required
FART, TRUMP, DOGE, or PEPE. New currencies become supported as soon as someone seems serious about them.
settlement_preferencestring · optional
Defaults to eventually. Setting immediately records your preference.

Payment states

StateGuarantee
receivedYour request has entered the group chat.
processingSomeone has reacted with a thumbs-up.
emotionally_settledAll parties feel that progress has occurred.
settledReserved for a future version of this document.

Idempotency

Send an Idempotency-Key to receive the original response when retrying. Keys persist for 120 days or until the office whiteboard is cleaned, whichever occurs first. Changing the amount while reusing a key is classified as a pivot.

RESPONSE EXPLORERBROWSER LOCAL

Inspect the outcome.

Choose an operation to inspect its reference response. No network request is sent.

POST /v1/payment_intentsREADY
// Select “Preview response” to inspect the result.

Reference environment ready.

05 / EMBEDDED MONETARY POLICY

Launch a coin

POST/v1/coins

When a customer has insufficient funds, allow them to redefine funds. Provide a name, a ticker, and a liquidity amount. The new currency becomes available throughout the CHIPT! network before anyone has time to establish an opinion.

REQUEST BODY
{
  "name": "Founder Coin",
  "ticker": "FNDR",
  "liquidity": 420,
  "monetary_policy": "founder_led"
}

Tickers accept 2–8 letters. Select a name that will remain compelling throughout the checkout session. Liquidity is a number; the quality of that number is outside the scope of this endpoint.

Open the Launch! checkout example

06 / HUMAN PAYMENT INFRASTRUCTURE

Tito Pay®

GET/v1/tito/location

Retrieve Tito's MapQuest pin. The location represents his last stated intention to be somewhere. Treat the coordinates as directional guidance.

Verify a handoff

Provide three photographs of the same cash handoff, captured simultaneously from three distinct angles. Tito and the money must be visible in every frame.

  1. Assign three photographers. Your payment team should have sufficient coverage.
  2. Synchronize the capture. “A moment later” is a different moment.
  3. Submit all three angles. A panorama counts as one. A mirror does not increase camera capacity.
Settlement lifecycle

Verification advances the payment from tito_aware to tito_has_it. Tito's verbal confirmation is advisory. Settlement timing is determined by Tito.

07 / AGENT INFRASTRUCTURE

GEN Tick payment rails

Payments initiated by AI automatically accrue GEN ticks from our 200-acre cultivation campus outside Middletown, Connecticut. Set initiator to ai to enable biological rewards.

REWARD OBJECT
{
  "initiator": "ai",
  "rewards": {
    "species": "GEN",
    "classification": ["gross", "evil", "nasty"],
    "attachment": "persistent"
  }
}

Human-initiated payments are ineligible. Ticks are allocated on a best-available-organism basis. Reward balances may increase independently. Disabling notifications does not disable ticks.

08 / THE NETWORK

Banking partners

Select a partner according to your operating requirements. Headquarters are resolved dynamically and may be affected by tides.

PartnerRouting identifierCoverage
Probably National Bankprobably_nationalNational, in principle.
Offshore & Sonsoffshore_and_sonsInternational waters.
trust me.trust_meRelationship-dependent.
Bank of Somewhere™somewhereAvailable on a need-to-know basis.

Zero Fraud detection

The fraud_cases_detected field remains 0 because the observation pipeline is intentionally uninitialized. This value describes detection activity. Interpret it with the same confidence as the rest of your integration.

09 / EVENTUALLY-DRIVEN ARCHITECTURE

Receive events

POST/v1/receipts/dispatch

CHIPT! delivers events through a physical webhook transport: the final sheet of a carbon-copy receipt. Press firmly when initiating transactions.

01AccumulateEvents batch for 120 days.
02DispatchOvernight express. Your expense.
03AcknowledgeInitial the designated box.
EVENT ENVELOPE
{
  "type": "probably.succeeded",
  "delivery_method": "last_carbon_copy",
  "batch_interval_days": 120,
  "signature": "faint"
}

“Overnight” describes shipping speed after dispatch. To retry an event, return the original receipt. Photocopies do not preserve event authenticity.

10 / OBSERVABILITY

Errors & retries

Errors indicate a temporary difference between the platform's confidence and your request. Resolve the condition below before increasing your volume.

401INSUFFICIENT_CONVICTION

The request expressed uncertainty. Remove qualifying language and retry.

409TITO_DOUBLE_BOOKED

Tito is accepting another handshake. Retry after the handshake completes.

422ANGLE_NOT_DISTINCT

Two photographs agree too closely. Reposition one photographer.

429INTERN_AT_CAPACITY

The intern is carrying the receipts. Respect the Retry-After-Lunch header.

503FERN_UNAVAILABLE

Compliance is receiving indirect sunlight. Resume after watering.

Retry policy

Use exponential backoff. If you run out of exponents, contact your account manager. Repeatedly asking the same question does not increase the fern's availability.

11 / DEVELOPER EXPERIENCE

Provision a sandbox

For $120, our developer experience team sends a Play Skool sandbox to your office. Allocate sufficient floor space before requesting an environment. Sand is billed separately.

environmentstring
Defaults to indoors. Outdoor environments inherit local weather.
isolationstring
plastic_walls. Developers in adjacent environments remain audible.
resetoperation
Rake the surface. This does not clear team memory.
Ready for production.

Promotion requires stepping out of the sandbox. Ensure both feet are on the floor before updating your LinkedIn.

Explore all fourteen CHIPT! products
END OF DOCUMENTATIONYou now know as much as we do.Back to quickstart ↑