Seeks to address

#205

Follows discussion with @aphillips

spec.bs

@@ -609,6 +609,7 @@ members:
               language or direction metadata associated with specific input
               members, in that it represents the caller's requested localized
               experience rather than assertion about a specific string value.
+	      See [[#sctn-i18n-considerations]] for more discussion.
 
     :  <dfn>showOptOut</dfn> member
     :: Whether the user should be given a chance to opt-out during the
@@ -1144,9 +1145,8 @@ contains the following members:
     :  <dfn>displayName</dfn> member
     :: The name of the payment instrument to be displayed to the user.
 
-         NOTE: For discussion about internationalization of the 
-         {{PaymentCredentialInstrument/displayName}}, see
-         <a href="https://github.com/w3c/secure-payment-confirmation/issues/93">issue 93</a>.
+         NOTE: See [[#sctn-i18n-considerations]] for discussion about
+         internationalization of the {{PaymentCredentialInstrument/displayName}}.
 
     :  <dfn>icon</dfn> member
     :: The URL of the icon of the payment instrument.
@@ -1540,3 +1540,22 @@ User agents render the {{PaymentCredentialInstrument/icon}} and {{PaymentCredent
 User Agents implementing this specification should follow both
 [[webauthn-3#sctn-accessiblility-considerations|WebAuthn's Accessibility Considerations]]
 and [=payment request accessibility considerations|PaymentRequest's Accessibility Considerations=].
+
+# Internationalization Considerations # {#sctn-i18n-considerations}
+
+Callers of the API may express preferences for localized transaction
+dialog experiences via the {{PaymentPaymentConfirmationRequest/locale}} member.
+
+This specification does not (yet) include mechanisms for callers to
+associate language or direction metadata with displayable strings
+provided as input to the API (e.g.,
+{{PaymentCredentialInstrument/displayName}}). To track progress on on
+this topic see <a
+href="https://github.com/w3c/secure-payment-confirmation/issues/93">issue
+93</a>.
+
+In the meantime, callers of the API should consider the following:
+
+* Aim for consistency between values of {{PaymentPaymentConfirmationRequest/locale}} (when provided) and the language of displayable strings.
+
+* If displayable strings contain or might contain [[i18n-glossary#def_bidirectional_text|bidirectional text]], ensure that they will display correctly without the application needing to process the contents of the string value via the insertion of Unicode bidirectional controls. For more information see [How to use Unicode controls for bidi text](https://www.w3.org/International/questions/qa-bidi-unicode-controls).