Repository navigation
docs: say what moneta's payment, standing order and token specifications settle - #70
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows #69 with the three specifications downloaded after it: `VipPISPPaymentsBatch_v4`, `VipPISPStandingOrders_v4` and `VipTokenIntrospect_v1`.
The one that changes the plan is introspection: `GET /api/v1/vip/token/introspect` returns a merchant token's expiry, so "how long a token lives" is no longer unknown, and `client.tokenExpiry(token)` goes into Next. Payments and standing orders are described as the specifications define them, including the trap that a payment request writes symbols as `VS:1,KS:2,SS:3` with commas while a movement reads them back with spaces. The stale "Balances" item in Next is gone; balances shipped.