Updating a payment API integration: field compatibility, signing regression and old-order checks

After formal account setup, a later document may add fields or change examples. That does not justify replacing code and configuration without review. Reconcile the document revision, enabled merchant configuration, application version and unfinished orders together. This guide promises no fixed WenFuPay version parameter, dual-version endpoint or compatibility period.

Continue by topic

List differences and confirm their actual scope

Keep dated or versioned references to both documents. Compare paths, methods, field names, types, required status, amount units, enums, signing and response rules. Confirm whether new fields enter the signature; “optional” does not mean harmless.

Ask which merchant, channel and environment the change applies to, when it activates and how old orders are queried and notified. An edited example need not change the protocol, while an unchanged field name may hide changed semantics. Text replacement is not an upgrade plan.

Test contract structure and business results separately

Formats such as OpenAPI describe HTTP interface structures. Passing structural validation does not prove correct signing, amounts, merchant ownership or delivery. A merchant can keep its own contract checklist without assuming that the platform publishes an OpenAPI file.

Use redacted cases for missing and extra fields, empty values, numeric types and unknown enums. Confirm how old clients handle additions under the real contract; neither silently ignoring every unknown field nor rejecting every extended valid notice is a universal policy.

Define old-order parsing and processing boundaries

Example: OLD-A is created under old configuration but completes after activation of a new one. Check its original configuration and the actual message contract confirmed by both sides. Receipt time does not prove a new format, and cycling through signing rules until one passes is not version selection.

Retain configuration references, scope boundaries and order associations without placing production keys in order snapshots or reports. Confirm retirement of old credentials and handlers, and reconciliation of pending orders, with the technical team. Upgrades must not erase paid or fulfilled facts.

Finish with executable launch and rollback checks

Cover new and pending old orders, notices and queries, repeated notices, unknown states, credit failures and rollback. Record expected and actual outcomes plus responsibility rather than one HTTP-success screenshot. Mark uncovered changes as not yet accepted.

Confirm formal material and switching arrangements with WenFuPay before deployment. On incompatibility, limit affected new operations, retain evidence and follow the agreed rollback. Rolled-back code must still handle orders already created under the new contract. Refunds, payouts and other capabilities need separate confirmation; a word appearing in documentation is not evidence of availability.

Frequently asked questions

Is an added optional field always safe for old systems?

No. It can affect signing, validation or semantics. Confirm enabled scope and regress old and new examples instead of relying on the word optional.

Can receipt date select the signature version?

Not alone. Old orders may notify after the switch. Use original configuration and agreed boundaries; escalate unknown cases instead of guessing.

References