What is the whole path from sign-up to live payments?
The Home page carries a progress panel mirroring this list, so you can leave and resume anywhere.
How do I create the account and verify my email?
Sign-up takes an email address and a password; the strength indicator checks for upper case, lower case, a digit and a minimum length. Google sign-in is offered as an alternative. Verification then arrives in one of two shapes, depending on how the account was created: a 6-digit code you type into the verification screen (paste works — the six boxes fill themselves), or a verification link you click in the email. A countdown runs before Resend becomes available again; if the code never arrives, resend once the countdown clears rather than signing up again — a second sign-up starts a new account. The Get started screen that follows asks only for your company legal name and incorporation country/region — enough to create your first record and begin preparing a sandbox. It reappears pre-filled later in account verification.What do the six Sandbox Setup steps ask for?
Steps are gated by progress: the wizard redirects you back to the furthest step you actually completed,
so you cannot deep-link past unanswered questions. Business type is a single-select list of
categories (AI/SaaS, gaming, e-commerce, streaming, education, travel, fintech, marketplace, social and
chat apps, digital content and more). Incorporation country on step 1 is a short card list — if yours
is not on it, use the Contact us link on that step rather than picking the nearest match.
How do product, pricing strategy and markets change what I can test?
They are inputs to the payment method list, not cosmetic. When you leave step 4 the Portal previews payment methods for the exact combination you selected, and step 5 renders only what comes back.
Two consequences worth knowing before you pick: subscription-only + Global USD pricing leaves no
local markets selectable, only the Global option; subscription-only + local currency pricing narrows
step 4 to the small set of markets where local-currency subscriptions are offered, with the remaining
market chips greyed out rather than hidden. Changing your product selection or pricing strategy after the
fact clears your downstream choices on purpose — the previous list is no longer valid.
Step 5 lists Country/Region, Product, Payment method type, Payment method, Order currency and Status,
filterable by country, method type and enabled/disabled. Popular methods come pre-enabled; every row you
leave enabled must have at least one order currency selected, or the step will not advance.
What is the difference between the Global market and a country?
Global sits in the market list next to the countries, but it is not one. It stands for the global card schemes, which do not belong to any single country, while every other entry in the list is a country or region whose local payment methods you want to test. The two are not alternatives, and this is the most common misreading of step 4:
Selecting Global does not clear your countries, and selecting a country does not clear Global. If
you intend to take card payments anywhere in the world and local methods in two markets, select
all three. On step 5 the global rows are grouped under a Global country label and sorted to the
top, so you can tell them apart from the country rows at a glance.
Why is a payment method I expected missing from step 5?
Step 5 does not query anything. The list is produced when you leave step 4, from exactly three inputs — your product selection, your pricing strategy, and your markets — and step 5 renders what came back. So work through the inputs in that order:
If the table comes back empty altogether, it renders as an empty table rather than an explanation —
go back to step 4 and widen the markets rather than assuming the step is broken.
Two things this step is not: it is not your production contract (see below), and it is not the
complete Waffo catalogue. What your live account can accept is
Service → Payin, and from code
/api/v1/paymethodconfig/inquiry — see
Payment Method Configuration & Limits.
If I turn a payment method off in the sandbox, does production change?
No. The wizard and Settings → Sandbox Config write your sandbox configuration only. What you can accept in production is your payin agreement, which is set up on Waffo’s side and read on Service → Payin — the wizard never writes to it. The implication runs both ways, and it is worth internalising before go-live:
A method that works in the sandbox and fails in production is the visible symptom of the first row;
Limits, Currency & Configuration Errors covers what
that failure looks like, and
Sandbox Environment & Access covers how the two
environments are isolated from each other.
The page says “Default configuration”. Can I test without configuring anything?
Yes. Settings → Sandbox Config carries one of two badges:
Read the actual default set off that page rather than from any document — it is what the page shows
you, and it is a starting point, not a commitment. Customize re-enters the wizard at step 1
seeded with the current values, and none of these controls touch your API credentials. What
Reset and Clear all do to an edit in progress, and how re-submitting replaces rather than
patches your selection, are in
Sandbox Environment & Access.
My submission came back with an error. What do I do?
The submission is all-or-nothing and the failure arrives as a single message rather than field-level errors, so there is no partial state to clean up. Your answers stay in the wizard: fix what the message names and submit again. Before submitting, one rule is enforced locally — every payment method you leave enabled must have at least one order currency selected, or the step refuses to advance and tells you so. That is the most common reason a submission cannot be attempted at all. If the final step reports that no sandbox configuration exists, it returns you to step 5. Nothing was lost: the submission never landed, so re-submit from there.Where do I get my sandbox credentials?
Step 6 polls for credential readiness every couple of seconds and shows a “setting up your sandbox” state until they exist. The poll has no timeout, so a page that spins for a long time is not counting down to anything — it is still waiting for readiness, and it is worth raising rather than waiting out. Once ready, the sandbox MID, API key and key material live under Settings → Integration → API Keys, and the test card library (success and decline scenarios only — there is no 3DS-challenge test card) under Settings → Integration → Test cards. If step 6 reports that no sandbox configuration exists, the wizard sends you back to step 5 to submit — the submission never landed; credentials were not lost. Afterwards, Settings → Sandbox Config exposes the same four decisions as an editable review flow. Re-submitting replaces the whole selected set rather than patching one row, and your API credentials are unaffected by a configuration change.What does account verification ask for?
/verify-account is a seven-step wizard (eight when extra documents are requested of you). Each step
must be complete before you continue:
Documents is not a fixed checklist. It always asks for a Certificate of Incorporation and the signing
director’s ID document, then adds a shareholding structure chart for corporate or mixed ownership, the
main contact’s ID document when that is a different person, and per-UBO ID document and proof of address.
Anyone already listed as signing director or main contact is not asked for the same ID twice. Accepted
formats are PDF, JPG, JPEG and PNG, each encrypted before storage. The size limit is shown on the Documents
panel itself — read it there rather than from this page, because it is enforced per uploader. Upload
colour images with clear, complete edges — every field has a Guidelines panel with a reference example.
Your answers are saved as a draft each time you continue, and reopening
/verify-account restores them,
uploaded files and reached step included. Submitting is the point of no return: the application enters
review and cannot be edited unless it is returned to you.
My application came back as Returned. What do I fix?
In returned mode the wizard is precise about scope: reviewer notes appear at the top, the step indicator
marks which steps contain returned items, individual fields and documents are flagged in place with the
note for that item, and everything else stays locked. A step stops being flagged once you address its
items, so the marks double as your to-do list. Fix them and re-submit — a re-submitted application counts
as in review again.
The Portal shows an email address and my integration has a support group. Which do I use?
They answer different halves of onboarding, and using the wrong one is the usual reason a question sits unanswered:
Acceptance in particular is group-only: the completed
acceptance template is
submitted to the technical support group and confirmed there — see also
Quickstart, which ends at the same place.
Stuck at a step, or an entry point missing from your Portal? Email support@waffo.com with the screen you are on.