What it means to integrate payments and issuing into your platform

Payment integration means connecting your platform to a system that processes transactions — so users can pay directly through your app or website instead of leaving to use PayPal or a bank. Card issuing means your platform can create and issue physical or digital cards that users hold in their own names, funded by their account balance or a connected bank account.

Together, these capabilities let you control the entire money flow: you collect payments from customers, hold the funds, and distribute them to users or vendors through cards or transfers. You become the intermediary between payer and payee, which means you also take on compliance responsibility for fraud, disputes, and regulatory reporting.

Most platforms do not build these systems from scratch. Instead, they use a payment processor (like Stripe, Square, or PayPal) for transaction processing, and a card issuer or issuing platform (like Marqeta, Galileo, or Lithic) for card creation and management. Some providers offer both in one package.

Key Takeaways

  • Payment integration requires choosing a processor, connecting their API to your system, and handling PCI compliance — the security standard for storing card data.
  • Card issuing requires a banking partner and an issuing platform; you do not issue cards directly but through a licensed intermediary.
  • Regulatory requirements vary by what you do: moving money between users triggers money transmitter rules in most states, while accepting customer payments does not.
  • Fraud and dispute handling become your responsibility once you integrate, so you need systems to detect unusual activity and respond to chargebacks.
  • Integration timelines range from weeks for basic payment processing to months for full card issuing, depending on your compliance profile and the provider's underwriting.

Choosing a payment processor and understanding what they do

A payment processor handles the technical and financial side of accepting money. When a customer enters a card number on your platform, the processor validates the card, checks with the customer's bank, holds the funds, and deposits them into your account. You pay the processor a percentage of each transaction (typically 2.2% to 3.5% plus a flat fee per transaction) plus monthly fees for access to their tools.

The major processors differ in what they support and who they target. Stripe and Square handle payments for most business types and offer APIs that let you build custom checkout flows. PayPal focuses on consumer-to-consumer transfers and marketplace payments. Adyen and Worldpay serve high-volume merchants. Smaller processors like Wise or Remitly specialize in cross-border transfers. Your choice depends on your transaction type, geography, and whether you need card issuing from the same provider.

When you sign up, the processor will ask about your business model, expected monthly volume, and what you do with the money. If you hold customer funds and distribute them later — as a marketplace, gig platform, or payroll service does — you will face stricter underwriting and higher fees. If you simply collect payment for your own goods or services, the process is faster.

How to connect payment processing to your platform

Integration starts with the processor's API documentation. You will build code that sends transaction details (amount, currency, customer ID, card token) to the processor's servers, receives a response confirming success or failure, and stores the transaction record in your database. Most processors provide client libraries in common languages (Python, JavaScript, Java) to speed this up.

Before you go live, you must handle PCI compliance — the Payment Card Industry Data Security Standard. This means you cannot store full card numbers on your own servers. Instead, you collect the card number on your frontend (using the processor's hosted form or tokenization library), send it directly to the processor, and receive back a token — a unique string that represents that card without exposing the number. You store the token and use it for future charges.

Testing happens in a sandbox environment where transactions are simulated but no real money moves. You test successful charges, declined cards, expired cards, and refunds. Once testing is complete, you apply for production access. The processor reviews your setup, confirms you are handling tokens correctly, and turns on live processing. This stage typically takes one to two weeks.

Understanding card issuing and how it differs from payment processing

Card issuing is separate from payment processing, even though they sound related. A payment processor lets customers pay into your platform. A card issuer lets your platform issue cards that customers use to pay out — to withdraw funds, make purchases, or transfer money to others.

You do not issue cards directly. Instead, you partner with a card issuer (Marqeta, Galileo, Lithic, or others) and a sponsoring bank — a licensed bank that holds the funds and backs the card network (Visa or Mastercard). The issuer handles the technical side: card design, PIN management, fraud detection, and real-time transaction authorization. The bank handles the legal and regulatory side: holding customer deposits, reporting to regulators, and managing chargebacks.

When a user requests a card through your platform, your system sends a request to the issuer's API. The issuer creates the card, assigns it a number, and either ships a physical card or displays a digital card number in your app. When the user swipes or taps the card, the merchant's bank contacts the issuing bank to confirm the funds are available. If they are, the transaction goes through; if not, it is declined.

Regulatory requirements that depend on what you do with money

The rules change based on whether you hold customer funds or just process payments. If you simply accept payment for your own product or service — a SaaS subscription, an e-commerce store, a ticket sale — you are a merchant. You need a payment processor and PCI compliance, but no special licenses.

If you hold customer money and move it between accounts — as a marketplace (connecting buyers and sellers), a payroll service, a gig platform, or a peer-to-peer transfer app does — you are likely a money transmitter. Money transmitter rules vary by state, but most states require you to register, maintain a surety bond, and file regular reports showing how much customer money you hold and where it is kept. Some states require $25,000 to $500,000 in net worth before you can register. Federal law (the Bank Secrecy Act) requires you to report suspicious activity and file reports on large transactions.

If you issue cards, you must work with a sponsoring bank and comply with card network rules (Visa and Mastercard set their own standards). You also inherit responsibility for fraud: if a user's card is used fraudulently, you are expected to detect it, block the card, and reimburse the user or dispute the transaction with the merchant's bank.

Before you integrate anything, consult a lawyer who specializes in payments. The difference between "merchant" and "money transmitter" is not always clear, and getting it wrong can result in fines or loss of your processing account.

Building fraud detection and dispute handling into your system

Once you process or issue payments, fraud becomes your problem. You need systems to detect unusual activity: a card used in two countries within an hour, a sudden spike in transaction volume, repeated failed attempts with different card numbers, or a card used for high-value purchases after months of small ones.

Most payment processors and card issuers provide fraud detection tools built into their APIs. You can set rules (decline transactions over a certain amount, flag transactions from new countries, require additional verification for high-risk patterns) and receive alerts when suspicious activity is detected. You can also integrate third-party fraud detection services like Kount or Sift that use machine learning to spot patterns you might miss.

Disputes happen when a customer claims a transaction was unauthorized or the merchant did not deliver what was promised. The customer's bank initiates a chargeback — a reversal of the transaction. You have a window (usually 7 to 10 days) to respond with evidence: a signed receipt, proof of delivery, communication with the customer, or a refund you issued. If your evidence is strong, you win the dispute and keep the money. If not, you lose the money and pay a chargeback fee (typically $15 to $100). Too many chargebacks can get your processing account closed.

Build a system to track disputes, store evidence automatically (delivery confirmations, customer emails, refund records), and respond before the deadline. Many processors provide a dashboard where you can upload evidence and track the status of each dispute.

Timeline and cost for integrating payments and issuing

Payment processing integration typically takes two to six weeks from start to live transactions. The first week is setup and API connection. The second week is testing in the sandbox. Weeks three to six are underwriting (the processor reviews your business and decides whether to approve you) and production setup. If you have a simple business model and low expected volume, you might go live in two weeks. If you hold customer funds or have high volume, underwriting can take a month or more.

Card issuing takes longer — usually two to four months. You must apply to the issuer, who conducts underwriting and connects you to a sponsoring bank. The bank conducts its own review, which can take weeks. Once approved, you integrate the issuer's API, test card creation and transactions, and go live. If you are also registering as a money transmitter in multiple states, add another two to six months for state approvals.

Costs vary widely. Payment processing fees are typically 2.2% to 3.5% per transaction plus $0.30 per transaction, plus monthly fees ($0 to $300 depending on the processor). Card issuing fees range from $0.50 to $3 per card issued, plus per-transaction fees (usually $0.05 to $0.25), plus monthly platform fees ($500 to $5,000 depending on volume and the issuer). Money transmitter registration costs $0 to $5,000 per state depending on the state's requirements. Budget for legal review ($2,000 to $10,000) and compliance consulting ($5,000 to $50,000 depending on complexity).

Frequently Asked Questions

Can I use multiple payment processors at once?

Yes. Some platforms use one processor for standard credit card payments and another for ACH transfers or international payments. This spreads risk and lets you optimize fees for different transaction types. Your accounting system must track which processor handled which transaction, and you must maintain PCI compliance across all of them.

What happens if my payment processor shuts down my account?

Your transactions stop processing immediately, and you lose access to your dashboard. You cannot refund customers or retrieve transaction history without contacting the processor's support team. To avoid this, monitor your chargeback rate (keep it below 1%), respond to disputes quickly, and stay in contact with your processor about any changes to your business model. Have a backup processor ready to switch to if needed.

Do I need a separate bank account for customer funds?

If you are a money transmitter, yes — most states require you to keep customer funds in a separate account from your operating funds. Your sponsoring bank (for card issuing) or payment processor will direct deposits into a designated account. You cannot mix these funds with your own revenue.

How do I handle refunds if I issue cards?

Refunds go back to the card as a credit, which appears as available balance within one to three business days. If the card has been closed, the refund goes to the original funding source (the customer's bank account). Your card issuer's API lets you initiate refunds programmatically, and you should track them in your system to match them against customer requests.

What if I want to issue cards in multiple countries?

Each country has its own card network rules, banking regulations, and money transmitter requirements. You will need separate sponsoring banks in each country and separate card issuing integrations. This is complex and expensive — most platforms start in one country and expand only after proving their model works. Consult a lawyer in each target country before you start.