Establishing session

000
Wicker Gateway v1

Payment gateway · v1

Scroll

Take money anywhere — one API.

Online checkout, card machines, payment links and recurring billing — one versioned API, one dashboard, one settlement. You hold Wicker keys and nothing else. We hold the processing relationship, the reconciliation and the parts that go wrong at 2am.

Sandbox is free and takes no card

120s

How long a card-machine charge waits for the customer — the answer is the outcome, not a promise

35evt

Signed webhook events, deduplicated by id, retried with backoff

11models

Supported terminal models, from countertop PIN pads to Tap to Pay on iPhone and Android

2env

Sandbox and live, resolved from the key you present — never from a request

What we optimize for

A gateway is judged on the day something goes wrong.

Taking a payment is the easy half. The half that costs money is the timeout that charges a cardholder twice, the refund the bank quietly refuses, the chargeback whose deadline passes unnoticed, the terminal that was unplugged an hour ago and still shows a green dot.

Every one of those is a silent failure. Wicker is built so that none of them can happen quietly — and each one has a test that provokes it on demand, because a recovery path nobody has executed is a recovery path that does not work.

See what we guard against

One payment, end to end

Follow $48.50
through the machine.

A single contactless tap at a counter, and every artifact it leaves behind — the same object at every depth, from the card to the line on your bank statement.

A payment card ending 4821, presented contactless.
01 · The card is presented — contactless, ··4821
The gateway approval: payment.succeeded, $48.50, reference PAY-000042, card ending 4821.
02 · The gateway answers — approved, $48.50 held
The printed receipt: $44.00 sale, $4.50 tip, $48.50 total, approved on a PAX A920PRO.
03 · The counter gets paper — tip included, EMV attached
A signed webhook delivery: POST to your endpoint, payment.succeeded, 200 OK on the first try.
04 · Your server hears about it — signed, delivered, 200
The payout: $48.50 captured, $1.71 fees, $46.79 net, settled to the bank account ending 0417.
05 · The bank line lands — $46.79 net, reconciled

Keep scrolling

Capabilities

Everything a small business actually charges for.

Six surfaces, one balance, one set of fees. Every one of them is a screen in the same dashboard — Payments, Subscriptions, Payment links, Terminals, Payouts and Disputes — so nothing you switch on arrives as a separate tool.

01

Online payments

A hosted card field you drop into your checkout. Raw card data never reaches your servers, which is what keeps you in SAQ-A scope.

SaleAuth + captureCard on file
02

Terminals

Register a card machine with the code on its screen, push an amount to it, and get the outcome back in the same call. Tips entered on the device are added to the authorized total, and the EMV block the networks require comes back with it.

EMVContactlessTap to Pay
03

Payment links

A page anyone with the address can pay on. No account, no session. Fixed or buyer-chosen amount, single-use or standing, with an expiry.

FixedVariableSingle-use
04

Subscriptions

A mandate against a card you already hold. Nothing is charged when you create it; the biller collects, and a failed collection walks a four-attempt dunning ladder — with the subscription flagged past due the whole way — instead of failing silently.

TrialsDunningPause / resume
05

Disputes

A chargeback arrives with a clock already running. Evidence uploads, deadline warnings and the outcome all land in one place — an unanswered dispute is forfeited, not judged.

EvidenceDeadlinesOutcomes
06

Payouts

Batches of settled payments, less our fees, paid to your bank account — every payment attributed to the batch that paid for it, and every batch reconciled to the money that arrived.

Daily batchesFee detailBank payout

01 / Online

A checkout that keeps card data out of your building.

The card field is a hosted frame. You collect a single-use token, post it with an amount, and get a payment back. Nothing sensitive crosses your servers, so your PCI obligation stays at the smallest questionnaire there is.

  • Sale, or authorize now and capture later
  • Store the card for reuse with one flag
  • Full and partial refunds with reserved headroom
  • Or key one by hand from New payment in the dashboard
An online checkout with a hosted card field, expiry and CVC, and a pay button.

02 / In person

Push an amount to the counter and let the card decide.

A card-machine charge stays open while the customer taps, and the answer is the outcome: 201 paid, 402 not taken, 504 nobody presented a card. A sleeping device is refused by name rather than becoming a decline your customer reads as yours.

  • Tips entered on the device, added to the authorized total
  • Cancel from the till returns a stuck terminal to its idle screen
  • Receipt data including the EMV block the networks require
A card-present flow: amount pushed to the terminal, card tapped, tip added, receipt issued.

03 / Links

Get paid by sending an address.

No integration, no account for the buyer. The token in the URL is treated as a credential rather than an id, a fixed link's price is read from our record so a buyer cannot underpay it, and a single-use link is spent by the first successful payment and says so to whoever opens it next.

  • Fixed price, or a range the buyer chooses within
  • Single-use or multi-use, with an expiry
  • Card, bank account, Apple Pay and Google Pay — you choose which
  • Your terms link on every page, by requirement
A payment link opened on a phone, with a shortened URL and a QR code beside it.

04 / Recurring

A mandate, not a saved button.

A subscription is a standing instruction to charge a credential we already hold — which is why there is no card form when you create one. Nothing is charged at creation. The biller collects on schedule, and two billers waking on the same subscription cannot both charge it.

  • Trials, cycle days and a fixed number of periods
  • Dunning ladder on failure, not a silent cancel
  • Consent recorded with the IP and timestamp we saw
A recurring billing timeline with succeeded periods, one failed period and its retry ladder.
A handheld card terminal showing an amount, with labeled EMV reader, contactless antenna, receipt printer and serial number.

Terminals

Hardware that is registered with the code on its screen.

There is no serial-number form and no activation step. The terminal shows a short code on its screen; you type it into the Terminals screen or POST /api/v1/devices, and the processor answers with what the hardware is and whether it is connected. From that moment it takes sales. A sale sent to it waits — up to two minutes — while the customer taps, and the answer is the outcome: paid, not taken, or nobody presented a card. Every model below is driven the same way.

Registration
The code on the terminal's screen
Codes
Single-use; a removed terminal gets a new one
Connection
Read live, shown with its age
Off switch
Local and instant, no terminal needed
Stuck sale
Cancel returns it to the idle screen
Response
201 paid · 402 not taken · 504 no card
LANE_3000 LANE_5000 LANE_7000 LANE_8000 AXIUM_DX8000 AXIUM_RX7000 SELF_2000 SELF_5000 VP3350 TAP_TO_PAY_IOS TAP_TO_PAY_ANDROID

The money path

From a tap to a bank line, with every step accounted for.

Step 01

Authorize

The card is checked and the amount is held. Nothing has moved yet, and the hold expires if you never capture it.

Step 02

Capture

You claim the hold, in full or in part. A sale does both at once; an authorization waits for you.

Step 03

Clear

The networks move the funds. Card is fast; bank debits stay pending for days and can still be returned.

Step 04

Settle

The period is batched. Every payment gets its cost attributed, across every page of entries — not just the first.

Step 05

Pay out

Net lands in your bank account, and a failure tells you something you can act on rather than something about our float.

Status

—

Captured

—

Fees

—

Net to bank

—

The dashboard

One dashboard your staff can be trusted with.

Roles that mean something, a Sandbox / Live switch that makes you type the word LIVE before it moves you, and a refund flow that will not let the same money go out twice.

The Wicker merchant dashboard: Net volume, Refunded, Approval rate and Awaiting payout tiles, a daily volume chart for the last 30 days, and a table of recent payments with their statuses.
A sandbox marker across the top of every screen, and it cannot be dismissed Merchant Admin · Merchant Member

Developers

A charge is one call. The hard parts are already decided.

Integer minor units, a mandatory idempotency key on anything that can move money, and an environment resolved from your credential rather than from a field somebody can typo.

Amounts are integers amountMinor

1050 is $10.50. Sending 10.50 is a 400, not a charge for eleven cents.

Retries are safe Idempotency-Key

Required on create, capture, void and refund. A replay returns the original response byte for byte with Idempotent-Replay: true.

The environment comes from the key

Never from a body, a query or a path — all of which the caller controls. A sandbox key cannot reach live data.

Rate limits are per credential

Not per IP, so your worker fleet behind one NAT is not sharing a budget with somebody else.

Optional request signing

X-Gateway-Signature over the method, the path and query, and the raw bytes you sent. Each signature is good once, inside a five-minute window in either direction.

curl -X POST https://api.wickerpay.com/api/v1/payments \
  -H "Authorization: Bearer $WICKER_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "amountMinor": 1050,
    "currency": "USD",
    "token": "tok_5f3a9c21b7e04d18",
    "statementDescriptor": "BLUE DOOR CAFE",
    "storeInstrument": true
  }'

Events

You are told what happened, in our words.

You never receive a raw payload from our processing partner. Events come in Wicker's own shape, signed with your secret, so our processor never becomes part of your integration contract.

Events being signed and leased, delivered to your endpoint, and retried with exponential backoff on failure.

Signed HMAC-SHA256

Over <timestamp>.<raw body>, keyed with your webhook signing secret — compare it in constant time and refuse anything outside a five-minute window. For the 24 hours after you rotate that secret we sign with both the old one and the new one and send both in the header, so accept the request if any value matches.

At-least-once X-Gateway-Event-Id

Deduplicate on the event id. A slow batch must never let a second dispatcher send the same event twice unnoticed.

Retried with backoff

Anything that is not a 2xx is retried on an exponential schedule. Every attempt is listed under Developers ▸ Deliveries with its status code, how long it took and the body your own server returned.

Replayable

Re-send any past delivery to your endpoint from that same Deliveries log while you are still building the handler.

payment.succeeded payment.failed refund.succeeded dispute.opened subscription.payment_failed settlement.approved payout.paid +30 more

Settlements

Gross minus fees minus refunds. Nothing rounded twice.

Fees are computed as decimals, and whether they round per transaction or once across the whole batch is a setting on your plan rather than something you inherit by accident. Either way, nothing is rounded twice. Every payment in a batch gets its cost attributed, including the ones past the first page of entries, which is the difference between a real margin and a batch that reads as pure profit forever.

Settlement objects in the docs
A settlement batch broken into gross, fees, refunds and the net paid to the bank.
A settlement batch closing — gross, fees and refunds resolving to a net figure — and paying out to a masked bank account, beside a ledger of recent payouts.

Payouts

Net leaves the batch and arrives in your bank.

The Payouts screen shows every batch and what it became: gross in, fees and refunds out, and the net that reached the account. A failure tells you something you can act on rather than something about our float, and it arrives as an event as well as a row.

payout.paid payout.failed Net to bank settlement.created

Disputes

The clock starts before you hear about it.

A chargeback arrives with a deadline already running. Everything you need to answer it — the claim, the payment behind it, the evidence and the outcome — sits on one screen.

A dispute lifecycle: the claim and the payment it came from, a countdown to the respond-by deadline, three evidence files with their upload outcomes including one refused after upload, and the won or lost result.
Evidence is capped at 8 files · 1 MB each · 10 MB total A dispute that expires without a response is lost, not judged

Failure states

The expensive things that happen quietly.

Each of these is silent, costs real money, and is covered by a test that provokes it on demand.

01

A charge that times out

The naive retry charges the cardholder twice. The key is held and the payment is recovered by its idempotency id instead of created again.

02

A refund the bank refuses

The merchant believes the customer was paid and the customer was not. The reservation is released so the refund can be re-issued rather than locking the money away.

03

A dispute whose webhook was dropped

Invisible to everyone until the deadline passes, at which point it is forfeited rather than judged. Deadlines are polled, not merely awaited.

04

Two billers waking on one subscription

Both charge the same period — a chargeback, a brand fee and a customer who cancels. A unique index rejects the second before anything is charged.

05

A biller that has been off for a week

Catching up would charge a monthly customer three times in one minute. Every charge is owed; every charge is a dispute. Collection is bounded to one period per cycle.

06

A settlement with more than one page

Most payments never get a cost attributed and, because an approved batch is never revisited, they read as profit forever. Every page is walked to the end.

07

A terminal that lost its connection an hour ago

It looks fine on the counter and refuses every sale. The connection is shown with the age of the reading, re-read on every open, and a sale sent to it is refused by name.

08

A card tapped in the same second we gave up waiting

Two minutes with no card and the request is cancelled at the terminal — but the tap may have landed. The payment is recorded unknown, not failed, and the poller recovers it rather than letting the till ring it twice.

Compliance and security: PCI SAQ-A scope, TLS, HMAC signing and idempotent writes.

Trust

Card data never lands where it would cost you.

The card field is a hosted frame, so the primary account number never touches your servers and your obligation stays at SAQ-A — the shortest questionnaire there is. Secrets are hashed, never stored in the clear, and shown to you exactly once. The annual PCI attestation the card networks still require is signed in the dashboard, under Compliance, and we warn you before it is due.

PCI SAQ-A TLS 1.2+ Hashed secrets Scoped keys PCI attestation Signed webhooks

Going live

Two decisions stand between you and a live charge.

Ours, and our processing partner's. They are separate, they happen in that order, and the dashboard shows you which one you are waiting on.

The path from signup to a first live charge: register, complete the five-step application, our review, activation of your processing account, and enabling live as a separate switch.
Consent is recorded at submission and cannot be added later Enabling live is a separate, deliberate switch

Pricing

One rate. Priced before the charge, frozen at the charge.

The terms that applied the moment a payment was taken are stored on the payment. Change a plan and future charges move; past ones do not, and your reports can still explain both.

Standard

For a business taking its first card payment this month.

2.9%+ 30¢

Per successful card charge

  • Online checkout and payment links
  • Full and partial refunds
  • Dashboard for up to 3 users
  • Daily settlement batches and scheduled payouts
  • Free unlimited sandbox
Start free
Most common

Counter

For a business with a till, a queue and a card machine.

2.6%+ 15¢

In store · 2.9% + 30¢ online, invoices, links and API

  • Everything in Standard
  • Terminals, tipping and receipts
  • Subscriptions with dunning (sandbox only for now)
  • Unlimited dashboard users, as Admin or Member
  • Dispute evidence and deadline alerts
Start free

Interchange plus

For volume that has outgrown a single blended number.

IC+ 0.35% + 8¢

Interchange passed through at cost

  • Everything in Counter
  • Line-item interchange on every batch
  • Custom settlement schedule
  • Named support contact
  • Volume rates on request
Talk to us

The standard offer is 2.6% + 15¢ per in-store payment and 2.9% + 30¢ per online, invoice, payment-link or API payment, plus $5 a month per merchant account, with no setup fee. The Merchant Terms and the merchant agreement you accept are what apply to your account; other rates shown are illustrative and are set per merchant on approval. Recurring billing is available in the sandbox only for now. Chargebacks and ACH returns are priced separately and itemized on the settlement they belong to. Fees for failed and voided authorizations are off by default; if a plan turns any of them on, they are disclosed on the plan before you are charged one.

Questions

Before you write any code.

Sandbox costs nothing and needs no card. Register, then work through the onboarding application — five short steps, saved as you go, so you can stop and come back. Submitting it is not the finish line: a reviewer reads it, usually within one to two business days, and it is that approval which opens your sandbox, issues API keys and unlocks the rest of the dashboard. Until then Onboarding and Settings are the only screens with anything behind them. Live processing then needs your production processing account activated on top, and going live is a separate, deliberate switch — the server refuses live charges until that account is active.
The outcome, once the customer has acted. The request pushes the amount to the terminal and stays open — up to two minutes — while they tap, insert or walk away. 201 means they paid; 402 means the sale did not happen and the record says why; 504 means nobody presented a card, the payment is unknown, and you poll it rather than ringing the sale again, because a tap in that same moment is recovered.
Not on a terminal. A tip entered on the device is added to the authorized total, so the settled amount can legitimately exceed your request. Always read the final amount off the payment object rather than off the request you sent.
No, and you should not. Pass storeInstrument: true on the first charge and the card is kept on file against the customer; read its paymentInstrumentId back from the customer and charge that later. The card number itself never reaches your servers — the field is a hosted frame, which is what keeps your PCI obligation at SAQ-A.
We retry on an exponential schedule and keep every attempt under Developers ▸ Deliveries, with the status code and the response body your server returned. Once you are back you can replay any delivery by hand from that same list. Delivery is at-least-once, so deduplicate on X-Gateway-Event-Id — that is the one duplicate you cannot recover from downstream. If the endpoint keeps failing we stop sending to it and say so at the top of the screen.
Deliberately not. Changing the interval, start date or trial end silently re-dates a mandate the cardholder already agreed to, and it retroactively changes what a billing period means. To change a schedule, cancel and create a new subscription — which is also the only version of that change you can describe to the customer honestly. Amount, cycle day and the stored card being charged can all be updated in place.
Your software agreement is with Fifty Three LLC, which trades as Wicker: the Merchant Terms. Card processing is provided by a third-party processor with a sponsor bank, and you accept the processor's merchant application and processing agreement separately; the Merchant Terms name them. That agreement governs settlement and funding, and Wicker does not receive or hold your settlement funds. We are who you call for support and the API you build against. You are never issued processor credentials and never call the processor directly — every request you make authenticates against Wicker keys.

Start your application today.

Sandbox costs nothing and needs no card. Register, work through the five-step application, and once a reviewer approves it — usually one to two business days — your sandbox opens and you can take a test payment.