Authentication is currently not supported. All endpoints are responding as if client has made an authenticated service-to-service API call, as in the records service calling directly to the wellness service. User-oriented API calls and real authentication support will be coming soon so any integrations will have to be revisited at that time.
This resource represents the set of payment cards whose information has been shared by a user with the system for the payment of bills and subscription fees. Users may call it directly to manage their own payment sources. Service calls are supported to take payment information shared by users during intake and record them as payment sources.
GET this route while authenticated as a user to retrieve a list of payment sources which have been previously added by, or on behalf of, the currently authenticated user.
POST a payment source representation to this route to create a new payment source. Invocation by an authenticated user will associate the new payment source with that user, while invocation by a service requires the client property be set such that the new payment source may be associated with its owner.
TODO: specify the exact members of the payment-source entity; currently endpoints are returning prototype representations or accepting anything for mock integration