@@ -236,13 +236,13 @@ public PaymentMethodDomain update(PaymentMethodDomainUpdateParams params, Reques
236
236
}
237
237
238
238
/**
239
- * Some payment methods such as Apple Pay require additional steps to verify a domain. If the
240
- * requirements weren’t satisfied when the domain was created, the payment method will be inactive
241
- * on the domain. The payment method doesn’t appear in Elements for this domain until it is
242
- * active.
239
+ * Some payment methods might require additional steps to register a domain. If the requirements
240
+ * weren’t satisfied when the domain was created, the payment method will be inactive on the
241
+ * domain. The payment method doesn’t appear in Elements or Embedded Checkout for this domain
242
+ * until it is active.
243
243
*
244
244
* <p>To activate a payment method on an existing payment method domain, complete the required
245
- * validation steps specific to the payment method, and then validate the payment method domain
245
+ * registration steps specific to the payment method, and then validate the payment method domain
246
246
* with this endpoint.
247
247
*
248
248
* <p>Related guides: <a
@@ -254,13 +254,13 @@ public PaymentMethodDomain validate() throws StripeException {
254
254
}
255
255
256
256
/**
257
- * Some payment methods such as Apple Pay require additional steps to verify a domain. If the
258
- * requirements weren’t satisfied when the domain was created, the payment method will be inactive
259
- * on the domain. The payment method doesn’t appear in Elements for this domain until it is
260
- * active.
257
+ * Some payment methods might require additional steps to register a domain. If the requirements
258
+ * weren’t satisfied when the domain was created, the payment method will be inactive on the
259
+ * domain. The payment method doesn’t appear in Elements or Embedded Checkout for this domain
260
+ * until it is active.
261
261
*
262
262
* <p>To activate a payment method on an existing payment method domain, complete the required
263
- * validation steps specific to the payment method, and then validate the payment method domain
263
+ * registration steps specific to the payment method, and then validate the payment method domain
264
264
* with this endpoint.
265
265
*
266
266
* <p>Related guides: <a
@@ -272,13 +272,13 @@ public PaymentMethodDomain validate(RequestOptions options) throws StripeExcepti
272
272
}
273
273
274
274
/**
275
- * Some payment methods such as Apple Pay require additional steps to verify a domain. If the
276
- * requirements weren’t satisfied when the domain was created, the payment method will be inactive
277
- * on the domain. The payment method doesn’t appear in Elements for this domain until it is
278
- * active.
275
+ * Some payment methods might require additional steps to register a domain. If the requirements
276
+ * weren’t satisfied when the domain was created, the payment method will be inactive on the
277
+ * domain. The payment method doesn’t appear in Elements or Embedded Checkout for this domain
278
+ * until it is active.
279
279
*
280
280
* <p>To activate a payment method on an existing payment method domain, complete the required
281
- * validation steps specific to the payment method, and then validate the payment method domain
281
+ * registration steps specific to the payment method, and then validate the payment method domain
282
282
* with this endpoint.
283
283
*
284
284
* <p>Related guides: <a
@@ -290,13 +290,13 @@ public PaymentMethodDomain validate(Map<String, Object> params) throws StripeExc
290
290
}
291
291
292
292
/**
293
- * Some payment methods such as Apple Pay require additional steps to verify a domain. If the
294
- * requirements weren’t satisfied when the domain was created, the payment method will be inactive
295
- * on the domain. The payment method doesn’t appear in Elements for this domain until it is
296
- * active.
293
+ * Some payment methods might require additional steps to register a domain. If the requirements
294
+ * weren’t satisfied when the domain was created, the payment method will be inactive on the
295
+ * domain. The payment method doesn’t appear in Elements or Embedded Checkout for this domain
296
+ * until it is active.
297
297
*
298
298
* <p>To activate a payment method on an existing payment method domain, complete the required
299
- * validation steps specific to the payment method, and then validate the payment method domain
299
+ * registration steps specific to the payment method, and then validate the payment method domain
300
300
* with this endpoint.
301
301
*
302
302
* <p>Related guides: <a
@@ -314,13 +314,13 @@ public PaymentMethodDomain validate(Map<String, Object> params, RequestOptions o
314
314
}
315
315
316
316
/**
317
- * Some payment methods such as Apple Pay require additional steps to verify a domain. If the
318
- * requirements weren’t satisfied when the domain was created, the payment method will be inactive
319
- * on the domain. The payment method doesn’t appear in Elements for this domain until it is
320
- * active.
317
+ * Some payment methods might require additional steps to register a domain. If the requirements
318
+ * weren’t satisfied when the domain was created, the payment method will be inactive on the
319
+ * domain. The payment method doesn’t appear in Elements or Embedded Checkout for this domain
320
+ * until it is active.
321
321
*
322
322
* <p>To activate a payment method on an existing payment method domain, complete the required
323
- * validation steps specific to the payment method, and then validate the payment method domain
323
+ * registration steps specific to the payment method, and then validate the payment method domain
324
324
* with this endpoint.
325
325
*
326
326
* <p>Related guides: <a
@@ -333,13 +333,13 @@ public PaymentMethodDomain validate(PaymentMethodDomainValidateParams params)
333
333
}
334
334
335
335
/**
336
- * Some payment methods such as Apple Pay require additional steps to verify a domain. If the
337
- * requirements weren’t satisfied when the domain was created, the payment method will be inactive
338
- * on the domain. The payment method doesn’t appear in Elements for this domain until it is
339
- * active.
336
+ * Some payment methods might require additional steps to register a domain. If the requirements
337
+ * weren’t satisfied when the domain was created, the payment method will be inactive on the
338
+ * domain. The payment method doesn’t appear in Elements or Embedded Checkout for this domain
339
+ * until it is active.
340
340
*
341
341
* <p>To activate a payment method on an existing payment method domain, complete the required
342
- * validation steps specific to the payment method, and then validate the payment method domain
342
+ * registration steps specific to the payment method, and then validate the payment method domain
343
343
* with this endpoint.
344
344
*
345
345
* <p>Related guides: <a
0 commit comments