Billing, invoices and status

Card payments are processed by Creem, our Merchant of Record: it sells and invoices the plan on our behalf, collects billing details and computes any VAT due on its own hosted checkout page, and takes the card number. The site's own checkout collects only what starts the order -- email, plan, and an optional single-country selection -- and never sees a card.

The key row is written before the payment completes, in a past_due state. That is why a key can appear on your dashboard showing Awaiting payment: it is not an error, and it needs nothing from you beyond finishing the payment. When Creem's webhook confirms the charge, the key activates.

A launch discount, where one is running, is applied automatically to a new monthly checkout: there is no code to type in. “For life” means what it says: the discounted rate persists for as long as that subscription stays active, not just for the first payment. It is not combined with the annual price, because the annual price is already a standing 25%-off discount for that interval; see Annual billing.

The current offer, if any, is published at GET /public/launch-offer, keyless, no account needed to check it. The same endpoint feeds the banner on /pricing, so the website never shows a discount that endpoint does not confirm is still running.

Join at affiliates.creem.io/join/jobopportunitiesapi. Creem reviews every application manually, usually within a few days. Once approved, Creem sets a 180-day cookie on your referral link and attributes any paid checkout within that window to you, for as long as the 12-month commission term runs. It works on every plan, monthly or annual: an annual referral earns a twelfth of the yearly commission each month, the same way the subscription itself is billed.

There is no fixed fee and no minimum. Creem pays affiliates directly from each sale, not us. Payouts run on the 1st and 15th, EUR 50 minimum balance, after Creem's own KYC check. Full terms and the FAQ are on /partners.

Because Creem sells and invoices on our behalf, the invoice for a Creem-billed order comes from Creem, not from Job Opportunities API -- and it is Creem, not us, that decides the VAT treatment and issues the document. This is the ordinary shape of a Merchant-of-Record relationship: the seller of record and the invoice issuer are the same party, and it is not us.

From your account page, a key billed through Creem shows a Manage billing button. It opens Creem's own customer portal, where a card on file can be changed and past invoices are listed -- Creem hosts that page, we only link to it.

For anything that is not self-service -- a refund, a question about a charge, a purchase-order reference -- /contact?topic=billing reaches a person, or Creem's own support can be contacted directly.

For the Viva-billed orders this still covers, the business is registered in Greece, so every issued document was transmitted to AADE's myDATA platform. That was always invisible to the customer; it is documented here only because it constrains the invoice, and two of those constraints occasionally surprised people.

A name was required on a retail document

The customer is a person, not a VAT number. The tax authority enforces this, so Viva-era checkout asked for a name even when a company VAT number was supplied.

Corrections were credit notes

A transmitted document cannot be edited. A correction is a new, related document.

A green dot on a conventional status page proves the site answered a probe. That is not the question a data buyer has. The question is whether the data moved, how much was re-verified in the last day, how much was added, how much was delisted, and how old the oldest verification is. Those are what /status reports, and all of them are read from the ledger.

The same figures are available programmatically at /public/status (keyless), and the deeper freshness report at `/public/freshness`.