Soft declines and retries
Timeouts, 'do not honor' and issuer errors are retried through a second route inside the same request. If that fails too, the payment is declined and the reason is on the record.
How it works · Payments
Seven steps separate a tap on Pay from money in your bank account. Most take milliseconds; only the payout to your bank waits for the next business day. Here is each one, what you see in the dashboard, and what can go wrong.
United States
Simulated hosted checkout for Northlight: Studio Lamp, $249.00, Card selected.
Pay Northlight
$249.00
Studio Lamp
Charcoal · brass hinge
Powered by SparkIOTermsPrivacy
Studio Lamp
$249.00
Payment method
Powered by SparkIOTermsPrivacy
en-US · USD · Frictionless 3DS
Same integration. Checkout adapts per country.
Step by step
Timings are typical, not promises. The exact figures for your account are in the dashboard, per method and country.
Timings and amounts are placeholders, not commitments.
At the customer's pace
The customer picks a payment method on your checkout, whether hosted, embedded or built on the API. The page already shows their currency, language and the methods common in their country. A payment record exists from this moment, but nothing has been charged.
You seeCreated
≈ 50 ms
Card details travel from the customer's browser straight to SparkVault and come back as a token. Your servers never hold a card number, which is what keeps you outside PCI scope. For returning customers we also request a network token from the card scheme, which keeps working when the plastic is reissued.
You seeTokenized
≈ 100 ms · longer with a challenge
The gateway scores the payment on velocity, device and history, then decides whether to authenticate. Where strong customer authentication applies, 3-D Secure 2 runs; most customers pass without seeing anything and only the risky ones get a bank challenge. A payment that fails risk stops here and is marked declined.
You seeAuthenticating
≈ 200 ms
We send the authorization through the best route for that card and country. The issuing bank answers yes or no and, on yes, holds the amount on the customer's card. If the first route returns a soft decline, a timeout or a 'try again', we retry through a second route before you see anything. A hard decline, such as a stolen card, is never retried.
You seeAuthorized
At authorization, or up to 7 days later
Capture tells the network to move the money. Most merchants capture in the same call as authorization. If you ship later, you capture when the order leaves, for the full amount or less. An authorization you never capture expires on its own and the hold disappears from the customer's card.
You seeCaptured
At capture · days for bank debits
Because SparkIO is the acquirer, captured funds land in your balance without passing through another company. The fee is deducted and itemized on the same line, in your settlement currency. Cards, Pix and UPI settle the moment they are captured; bank debits and vouchers show as Pending until the money arrives.
You seeSettled
Instant, T+1 or on your schedule
Payout moves your available balance to your bank account on the schedule you set: the next business day (T+1), a day of the week, or instantly for a fee set in your pricing. Each payout lists the payments it contains, so matching it against your bank statement is a filter in the dashboard, not a spreadsheet.
You seePaid out
Where the money is
Finance teams trip on this one: an approved payment is not cash yet. Your balance shows each amount in the state it is actually in, so the number you can pay out is never a guess.
Available
$1,101.47
Pending $408.70
Next payout · Thu, Oct 22
Simulated balance. Each line is a filter in the real dashboard.
When things go wrong
Each case has a status, a reason and a next action in the dashboard. None of them needs a support ticket to understand.
Timeouts, 'do not honor' and issuer errors are retried through a second route inside the same request. If that fails too, the payment is declined and the reason is on the record.
Stolen card, closed account, invalid number. These are final and never retried; retrying would only hurt your standing with the issuer.
Full or partial, from the dashboard or the API. The money returns along the route it came: Pix is instant, cards take a few business days to show it on the statement.
A cardholder asks their bank to reverse a payment. The amount is held, you get the deadline and an evidence form in the dashboard, and the card network decides.
An authorization you do not capture within the network's window lapses on its own. The hold drops off the customer's card and nothing is charged.
Ship two of three items, capture two thirds. The rest of the authorization is released, and the customer is charged only what you captured.
Questions
Sandbox keys and test cards for every step, including declines and disputes.