Terms of service
The terms on which WinkPG is made available, and what each side is responsible for.
The WinkPG platform default. An operator may replace it with their own text. Last reviewed 20 September 2026.
What these terms are
These are the platform's standard terms. A signed agreement between you and the operator of this WinkPG instance takes precedence over anything on this page, and where the two differ the signed agreement governs.
This page exists so that a reviewer can read the shape of the arrangement without waiting for a contract to be sent.
Using the service
You may use the platform for the payment processing your account was boarded for. You are responsible for the accuracy of the merchant and settlement details you supply.
You may not use it to process a transaction that is prohibited by the card networks, by your acquirer or by law. You may not attempt to circumvent a rate limit, a permission boundary or an authentication control.
Credentials are yours to protect. Keep an API key out of client-side code and out of a public repository, rotate one you believe is exposed, and tell the operator when you do.
Sandbox and production
A sandbox credential can only reach the sandbox, and the platform refuses to run an interactive tool against a live credential rather than trusting a caller to choose correctly.
Sandbox data carries no retention guarantee and may be reset. Do not keep anything in a sandbox that you need later.
Fees and settlement
Fees, the settlement schedule and the reserve terms are set by the agreement you signed, not by this page. Surcharge and convenience fee arrangements are governed by card network rules and by the law of the jurisdiction the transaction is taken in, and a merchant is responsible for the configuration they enable.
Availability
The platform publishes a status page and a machine-readable status feed, and service level commitments are set by the agreement you signed. Where an agreement states none, the service is provided on a reasonable efforts basis.
Planned maintenance is announced in advance through the channels your agreement names.
Changes to the service
The platform treats a published interface as a contract. A change to a published route, payload, webhook event, error code or setting name is made compatibly wherever a compatible construction exists, and a break that cannot be avoided is announced with a migration path before it ships. The public changelog carries both.
Suspension and termination
An account can be suspended where continued use would breach card network rules, expose the platform or its other customers to loss, or follow from a compelling legal requirement. Where the circumstances allow it, notice is given first.
On termination, transaction records are retained for the period the retention schedule states, because financial regulation and chargeback rights outlive the account.
Liability
Nothing on this page limits a liability that cannot be limited by law. Every other limit and exclusion is the one your signed agreement sets.
Evidence and compliance materials
This surface states posture and publishes no evidence. The attestations, reports and control matrices behind these statements are in the trust documents catalogue, where a signed-in developer account can retrieve them and every retrieval is recorded.