Wicker™

API AND DEVELOPER TERMS

Wicker™ API and Developer Terms

Effective October 29, 2026

1. Authorized integration

Use the documented merchant API only for your approved business and authorized data. You remain responsible for developers acting for you and for their compliance with these terms. A developer working for several merchants must keep their data, credentials and authorizations separate. The public integration surface is the documented versioned API; internal portal endpoints are not a supported integration contract. Documentation describes intended technical behavior and is not a guarantee of production approval or continuous availability.

2. Credentials and environments

Store secret API credentials and webhook signing secrets only in appropriately protected systems. Do not embed secret keys in browser code, mobile binaries, public repositories, URLs or support messages. A public tokenization key has a different purpose from a secret API credential. Restrict access, review usage, rotate credentials after suspected exposure and revoke unused access. We may restrict or revoke compromised or abusive credentials.

Sandbox and production have separate logical scopes and credentials. Do not use real customer credentials or live personal information for sandbox tests. Objects created in sandbox do not establish live authorizations and must not be treated as live records. A live key alone does not activate processing; the merchant, processor account, integration and channel must be approved and enabled. Verify the intended environment before every deployment and before creating payment or webhook instructions.

3. Secure payment requests

Use approved hosted payment fields or approved devices to obtain payment tokens. Do not send raw card numbers or card security codes to general API endpoints. Keep amounts, currency, order references and customer authorizations accurate. A saved instrument must be scoped to the correct merchant and environment and used only within the customer's authorization.

Follow current request-signing requirements. For signature-required keys, sign the exact transmitted bytes and keep clocks synchronized; the reviewed implementation documents a five-minute timestamp tolerance. Do not disable verification to work around an integration error. Follow the current documentation for the signature format and rotation.

For an operation requiring idempotency, generate one key for the logical operation, save it with your business record, and reuse it for retries of that same request. Do not generate a new key merely because a response timed out. Compare authoritative transaction state and reconcile uncertain outcomes before attempting another charge. The reviewed request record has a roughly 24-hour expiry; this is not an indefinite duplicate-charge guarantee. Maintain your own durable operation and fulfillment records.

4. Limits and reliability

Observe rate-limit responses, use bounded backoff and avoid excessive polling. Limits may vary by route, account and deployment and may change for security or capacity. The locally reviewed API limiter is configured for 600 requests per minute per merchant, with separate tighter authentication controls; this is an implementation observation, not a purchased throughput entitlement or service-level commitment. Do not use multiple keys or accounts to evade limits.

We may change or retire API features with reasonable notice where practicable, subject to urgent legal or security needs. Build tolerant handling for additional fields and unknown events.

5. Webhooks

Register only endpoints you control or are authorized to use and secure production endpoints with HTTPS. Select the events you need and avoid forwarding unnecessary personal data. Verify signatures over the raw received body, validate timestamps, use constant-time comparison, and handle valid overlapping secrets during rotation. An API-key secret and a webhook signing secret are not interchangeable.

Design for duplicate, delayed, missing and out-of-order events. Persist and deduplicate event references before fulfillment; acknowledge only after durable handling or durable queuing. Delivery retries are bounded and may be exhausted, and failing endpoints may be disabled. Monitor your endpoint and reconcile from the API and processor records. Neither a webhook nor an HTTP success alone guarantees final settlement or freedom from reversal.

Do not return secrets or personal information in error bodies. The reviewed sender does not retain response-body content, although its model has a field and the developer page describes broader recording; do not depend on logging behavior remaining unchanged.

6. Data and acceptable use

The Acceptable Use Policy, Privacy Notice and adopted Data Processing Addendum apply. Do not scrape unrelated data, test unauthorized systems, defeat tenant controls or misrepresent approval. Restrict data to the approved purpose, protect it in transit and at rest as appropriate, and meet your legal duties to customers. Report suspected compromise promptly through support. No API field, consent flag or metadata value waives a required legal authorization.

7. Recurring billing and closure

Recurring API calls require the separate program and consent gates. Maintain the actual customer disclosure, affirmative acceptance, notices, cancellation and revocation evidence outside any field that cannot represent it fully. Merchant-originated IP and browser details are evidence of the merchant request, not proof of the cardholder's identity or assent. Updating an amount in software does not obtain consent to the change.

On termination, stop new charges, cancel future instructions as appropriate, revoke credentials and disconnect endpoints after necessary reconciliation. Preserve records required by the accepted agreements and law. These terms do not authorize retention of raw payment credentials or continuation of charges after consent is withdrawn.

8. Release and responsibility

The Merchant Terms govern licensing, liability, disputes and termination. Test signature rejection, duplicate handling, uncertain-payment reconciliation, cancellation and environment separation before requesting live approval. Sandbox success, a source-code review and this document are not live acceptance. Contact support@wickerpay.com for integration support; no support-hours or response-time commitment is implied.