---
title: "Stripe connected merchants"
slug: "stripe-connected-merchants"
updated: 2026-06-02T14:35:33Z
published: 2026-06-02T14:35:33Z
canonical: "api-docs.blinkpayment.co.uk/stripe-connected-merchants"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs.blinkpayment.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe connected merchants

Some Blink merchants are configured to process card payments through Stripe while still using Blink as the customer-facing payment layer.

For these merchants, the card payment implementation differs from the standard Blink card flow. The integrator should still create a Blink payment intent as normal, but they do not submit the card payment to the `/api/pay/v1/creditcards` endpoint.

Instead, the integrator should render the card payment `ccElement` or `ccMotoElement`returned in the payment intent response. When the customer submits the rendered form, Stripe processes the payment and then communicates the result back to Blink.

The merchant’s integration should continue to rely on the Blink `return_url`, `notification_url`, transaction status, and transaction reporting for post-payment handling.

#### Stripe-connected card payment flow

1. Create an access token.
2. Create a payment intent with `payment_type` set to `credit-card`.
3. Render the relevant card element returned in the intent response.
4. Allow the customer to complete and submit the rendered payment form.
5. Stripe processes the card payment.
6. Blink receives the payment result from Stripe.
7. Blink updates the transaction and sends the configured return/notification updates.

> [!CAUTION]
> Important: Stripe-connected merchants should not use the `/api/pay/v1/creditcards` resource for card payment submission. That endpoint is used for the standard Blink card processing flow.

See a demo of the Blink API connected to Stripe [here](https://github.com/Blink-Payment/Blink-Stripe-Example-).