Skip to content

Commit 3131189

Browse files
horghclaude
andcommitted
Fix capitalization, punctuation, and formatting in minFraud API requests documentation
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 05f71d3 commit 3131189

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/minfraud/api-documentation/requests.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -264,7 +264,7 @@ transaction.
264264
{{</minfraud-schema-row>}}
265265

266266
{{< minfraud-schema-row key="shop_id" type="request" valueType="string" valueTypeNote="max length: 255" >}}
267-
Your internal ID for the shop, affiliate, or merchant this order is coming from. Required for minFraud users who are resellers, payment providers, gateways and affiliate networks. No specific format is required. However, if you are testing the minFraud service, please add a `test` prefix to your shop ID (e.g. `testfoo23` or `test:foo23`) or set your shop ID to `test` if you don’t have a shop ID.
267+
Your internal ID for the shop, affiliate, or merchant this order is coming from. Required for minFraud users who are resellers, payment providers, gateways, and affiliate networks. No specific format is required. However, if you are testing the minFraud service, please add a `test` prefix to your shop ID (e.g. `testfoo23` or `test:foo23`) or set your shop ID to `test` if you don’t have a shop ID.
268268

269269
[Learn more about the /event/shop\_id input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/event-and-account-inputs-minfraud#storefront-identifier)
270270
{{</minfraud-schema-row>}}
@@ -833,7 +833,7 @@ end-user and the payment processor about the credit card used for the event.
833833
{{</minfraud-schema-row>}}
834834

835835
{{< minfraud-schema-row key="was_3d_secure_successful" type="request" valueType="boolean" >}}
836-
Whether the outcome of 3-D Secure verification (e.g. Safekey, SecureCode, Verified by Visa) was successful. `true` if customer verification was successful, or `false` if the customer failed verification. If 3-D Secure verification was not used, was unavailable, or resulted in another outcome other than success or failure, do not include this field.
836+
Whether the outcome of 3-D Secure verification (e.g. SafeKey, SecureCode, Verified by Visa) was successful. `true` if customer verification was successful, or `false` if the customer failed verification. If 3-D Secure verification was not used, was unavailable, or resulted in another outcome other than success or failure, do not include this field.
837837

838838
[Learn more about the /credit\_card/was\_3d\_secure\_successful input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/credit-card-and-payments-inputs-minfraud#payment-processor-information)
839839
{{</minfraud-schema-row>}}
@@ -1004,12 +1004,12 @@ the input and issue a warning.
10041004
{{< schema-table key="custom_inputs" >}}
10051005

10061006
{{< minfraud-schema-row key="your_custom_BOOLEAN_key" type="request" valueType="boolean" >}}
1007-
A custom key of your choice, with a boolean value.
1007+
A custom key of your choice with a boolean value.
10081008
{{</minfraud-schema-row>}}
10091009

10101010

10111011
{{< minfraud-schema-row key="your_custom_FLOAT_NUMBER_key" type="request" valueType="float" valueTypeNote="min: -1e14, max: 1e14" >}}
1012-
A custom key of your choice, with a floating-point number value.
1012+
A custom key of your choice with a floating-point number value.
10131013
{{</minfraud-schema-row>}}
10141014

10151015

0 commit comments

Comments
 (0)