Authorize Payment results in the Hold. The diagram is representing a standard Auth + Capture credit card flow. Capture contains the final transaction amount an

Authorize Payment results in the Hold. The diagram is representing a standard Auth + Capture credit card flow. Capture contains the final transaction amount and can either be higher or lower than the Authorized amount. The odd thing is the Trip Service shouldn't know anything about the Issuer. That's the Payment Service's reason to exist (so Trip Service doesn't need to know about different payment methods). That the Trip Service knows how to talk to Visa (and Amex, and MasterCard, and Discover, and Google, and Apple) about Auth'ing a card, but doesn't know how to Capture the payment is the strange part. My expectation is that the diagram is incorrect, and the TripService talks to the PaymentService to Auth the card.