Before an application
Use the underwriting guide to organize legal, product, ownership, fulfillment, and processing evidence before a partner review.
Payment technology resources
Plain-language guides for teams building and operating embedded payments.
These articles explain payment infrastructure, partner roles, merchant onboarding, and integration controls without suggesting that program rules or approval decisions can be bypassed.
Use the library well
Start with the question your payment team needs to answer.
These guides are written for founders, operators, and developers who need to explain a payment path clearly. Each one separates the job of the gateway, processor, acquirer, merchant, and operations layer so a useful next step is easier to identify.
Before an integration
Use the gateway and tokenization guides to keep card collection upstream and define safe server-side responsibilities.
Before you rely on a result
Read the boundaries carefully. A request, token, or browser return is not the same thing as an approved merchant account or settled payment.
Payments guide
Payment Gateway vs Payment Processor
Understand the difference between a payment gateway, payment processor, acquirer, and the merchant operations layer around payment acceptance.
Read guidePayments guide
Merchant Underwriting Explained
Learn what merchant underwriting evaluates, why legal elevated-risk businesses may need more information, and how to prepare a credible application.
Read guideDeveloper guide
Payment Tokenization Explained
An overview of payment tokenization, hosted payment fields, and the role of tokenized references in a security-conscious payment integration.
Read guideWhat these guides do not replace
Public education cannot replace a partner's underwriting criteria, legal advice, processor documentation, or a merchant's own customer and data policies. Use the guides to ask better questions, then confirm the answer with the party that owns the decision.
Discuss your payment path