Fiserv Loyalty & Rewards mock API and live sandbox

Schema truth. Each response enumerates every field its contract can carry, so deserializers get exercised against the complete shape rather than a lucky subset — the bonus-history record alone materializes dozens of fields a terser fixture would omit. The flip side: nothing is arithmetic-checkable, since amounts are strings reading "sample". Bind models and assert presence here; put real point balances behind a private WireMock Cloud copy when tests need numbers that add up.

redeemBonus is the processor-native RPC — its response is a messages block with a result code and transaction status, the host's way of confirming an execution. The orders and points routes are the VISA Rewards Redemption Platform contract instead: a responseData object pairing request and response transaction ids with merchant identifiers, a points bank, and a customer loyalty balance. Clients typically implement one or the other; the sandbox carrying both lets an integration verify it chose — and parses — the right grammar before certification.

Program operations at scale. Issuers rebuild loyalty configurations each cycle — rules, tiers, behaviors, distribution buckets, capping — and the cycle-copy suite reads and writes those setups wholesale. Its responses here are the template's deepest: a get answers with a complete programsResponse nested inside the outer envelope, its own processorInfo included, which is exactly the double-wrapped shape configuration tooling must unwrap. Worth noting for test design: the family is get-and-put pairs, so round-trip tooling can be exercised contract-first without any state.

Through servicing surfaces like the Card Developer template, whose uChoose routes report redeemable balances and whose offers routes activate merchant deals — that's the cardholder-facing slice. This template is the program engine behind it. The shared envelope grammar with the Operations Execution template is no accident either: both are Issuer Solutions surfaces, but where that one answers with empty scaffolds, this one fills every shape — start model-binding work here.