Using Static QR

Generating a QR code for payment collection traditionally means assembling dozens of network-specific fields — merchant category codes, tax breakdowns, acquirer identifiers, terminal IDs, alias types — and encoding them into a TLV payload that follows the correct national standard. Every country has its own specification (EMVCo in Colombia, PIX in Brazil, PromptPay in Thailand), and getting a single field wrong produces a QR that scanners reject silently.

With Minka, the merchant already described who they are when they created their wallet. Creating a static QR is pointing to that wallet and saying this is a permanent payment point. The bridge reads the merchant profile — name, city, category, tax regime — maps the category to an MCC, detects the alias type from the taxId, and generates the complete network payload. The merchant never touches tag numbers, GUID prefixes, or country-specific tax condition codes.

What you're building

In this guide you'll create a static QR code: a permanent sticker for a store counter that customers scan with their bank app and enter the amount themselves. It uses the qr-static anchor schema, which tells the bridge to generate a reusable payload with point-of-initiation set to 11. The code never expires and can be used for unlimited payments.

Prerequisites

• A merchant wallet already created with a complete profile
• SDK credentials and a connection to a ledger
• The qr-static anchor schema deployed on the ledger
• A QR bridge connected and configured with a processing policy for anchor enrichment

Create a static QR code

A static QR is a permanent payment point. Print it as a sticker, table tent, or receipt footer. The customer scans it with their bank app and enters the amount themselves. It never expires and can be used for unlimited payments.

minka anchor create

curl -X POST "https://{ledger-host}/v2/anchors" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {your-token}" \
  -H "x-ledger: {your-ledger}" \
  -d '{
    "data": {
      "handle": "qr0000001@starbucks.com",
      "schema": "qr-static",
      "target": "store1@starbucks.com"
    }
  }'

// SDK setup: see How to Connect to a Ledger
// /moving-money/connect-to-ledger
const { response } = await sdk.anchor
  .init()
  .data({
    handle: 'qr0000001@starbucks.com',
    schema: 'qr-static',
    target: 'store1@starbucks.com',
  })
  .hash()
  .sign([{ keyPair }])
  .send()

import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;

HttpClient client = HttpClient.newHttpClient();

String json = """
    {
      "data": {
        "handle": "qr0000001@starbucks.com",
        "schema": "qr-static",
        "target": "store1@starbucks.com"
      }
    }
    """;

HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://{ledger-host}/v2/anchors"))
    .header("Content-Type", "application/json")
    .header("Authorization", "Bearer {your-token}")
    .header("x-ledger", "{your-ledger}")
    .POST(HttpRequest.BodyPublishers.ofString(json))
    .build();

HttpResponse<String> response = client.send(
    request, HttpResponse.BodyHandlers.ofString());

using System.Net.Http;
using System.Text;

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("Authorization", "Bearer {your-token}");
client.DefaultRequestHeaders.Add("x-ledger", "{your-ledger}");

var json = """
    {
      "data": {
        "handle": "qr0000001@starbucks.com",
        "schema": "qr-static",
        "target": "store1@starbucks.com"
      }
    }
    """;

var content = new StringContent(json, Encoding.UTF8, "application/json");
var response = await client.PostAsync(
    "https://{ledger-host}/v2/anchors", content);
var body = await response.Content.ReadAsStringAsync();

minka anchor read qr0000001@starbucks.com

curl "https://{ledger-host}/v2/anchors/qr0000001@starbucks.com" \
  -H "Authorization: Bearer {your-token}" \
  -H "x-ledger: {your-ledger}"

// SDK setup: see How to Connect to a Ledger
// /moving-money/connect-to-ledger
const { anchor } = await sdk.anchor.read('qr0000001@starbucks.com')

console.log(anchor.data.custom.qr.payload)      // full TLV string — encode into a QR image
console.log(anchor.data.custom.qr.paymentId)     // network transaction ID for inbound routing
console.log(anchor.data.custom.qr.generatedAt)   // when the payload was generated

import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;

HttpClient client = HttpClient.newHttpClient();

HttpRequest request = HttpRequest.newBuilder()
    .uri(URI.create("https://{ledger-host}/v2/anchors/qr0000001@starbucks.com"))
    .header("Authorization", "Bearer {your-token}")
    .header("x-ledger", "{your-ledger}")
    .GET()
    .build();

HttpResponse<String> response = client.send(
    request, HttpResponse.BodyHandlers.ofString());

using System.Net.Http;

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("Authorization", "Bearer {your-token}");
client.DefaultRequestHeaders.Add("x-ledger", "{your-ledger}");

var response = await client.GetAsync(
    "https://{ledger-host}/v2/anchors/qr0000001@starbucks.com");
var body = await response.Content.ReadAsStringAsync();

What happens after the customer pays

The payment flow is fully automatic once the QR exists.

The customer's bank sends a payment through the connected network. The payment message carries the QR's paymentId — the unique identifier the bridge embedded in the payload.

The ledger receives the inbound intent. An external bridge (ACH, RBM, or whatever network the customer's bank uses) creates an intent that moves funds from the customer's bank to the hub bank's settlement account (svgs:1234@bank.co).

The settlement effect fires. When the inbound intent commits, an effect triggers the QR bridge. The bridge looks up the anchor by paymentId (via the meta.labels reverse index), resolves it to store1@starbucks.com, walks up to the merchant wallet for the settlement field (svgs:4242@bank.co), and creates a second intent that credits the merchant's bank account.

The merchant is notified. When the merchant credit intent commits, a second effect fires, and the bridge sends a notification to the POS terminal or merchant app.

Two intents, two commits, fully atomic. Intent 1 reflects the network movement (auditable, matches bank reconciliation). Intent 2 is the internal book entry (merchant gets credited). If either fails, both roll back.

What you learned

• How to create a static QR anchor with just a target wallet reference
• How the bridge reads the wallet hierarchy and generates the complete EMVco payload with point-of-initiation 11
• How the two-intent settlement pattern credits the merchant automatically after each scan

Common errors

Next steps

• Collect with a Dynamic QR — generate a per-transaction QR with a fixed amount embedded
• Onboard a Merchant — set up the merchant wallet that QR anchors point to
• About Schemas — how anchor schemas control what the bridge generates