lxbfYeaa/PayPal-PHP-Server-SDK
Template
1
0
Fork 0
forked from LiveCarta/PayPal-PHP-Server-SDK
Code Pull Requests Activity

1.1.0 Release (#44)

Browse Source 
* Automated commit message

* add changelog

---------

Co-authored-by: PayPalServerSDKs <server-sdks@paypal.com>
Co-authored-by: Patrick Powers <patickpowers@hey.com>
This commit is contained in:
Patrick Powers
2025-05-27 13:31:17 -05:00
committed by GitHub
parent 671a2b2e5a
commit 6da8b9b5b8
234 changed files with 3130 additions and 1544 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/models/payment-method-preference.md
View File

@@ -11,8 +11,8 @@ The customer and merchant payment preferences.
| Name | Type | Tags | Description | Getter | Setter |
| --- | --- | --- | --- | --- | --- |
| `payeePreferred` | [`?string(PayeePaymentMethodPreference)`](../../doc/models/payee-payment-method-preference.md) | Optional | The merchant-preferred payment methods.<br>**Default**: `PayeePaymentMethodPreference::UNRESTRICTED`<br>**Constraints**: *Minimum Length*: `1`, *Maximum Length*: `255`, *Pattern*: `^[0-9A-Z_]+$` | getPayeePreferred(): ?string | setPayeePreferred(?string payeePreferred): void |
| `standardEntryClassCode` | [`?string(StandardEntryClassCode)`](../../doc/models/standard-entry-class-code.md) | Optional | NACHA (the regulatory body governing the ACH network) requires that API callers (merchants, partners) obtain the consumer’s explicit authorization before initiating a transaction. To stay compliant, you’ll need to make sure that you retain a compliant authorization for each transaction that you originate to the ACH Network using this API. ACH transactions are categorized (using SEC codes) by how you capture authorization from the Receiver (the person whose bank account is being debited or credited). PayPal supports the following SEC codes.<br>**Default**: `StandardEntryClassCode::WEB`<br>**Constraints**: *Minimum Length*: `3`, *Maximum Length*: `255` | getStandardEntryClassCode(): ?string | setStandardEntryClassCode(?string standardEntryClassCode): void |
| `payeePreferred` | [`?string(PayeePaymentMethodPreference)`](../../doc/models/payee-payment-method-preference.md) | Optional | The merchant-preferred payment methods.<br><br>**Default**: `PayeePaymentMethodPreference::UNRESTRICTED`<br><br>**Constraints**: *Minimum Length*: `1`, *Maximum Length*: `255`, *Pattern*: `^[0-9A-Z_]+$` | getPayeePreferred(): ?string | setPayeePreferred(?string payeePreferred): void |
| `standardEntryClassCode` | [`?string(StandardEntryClassCode)`](../../doc/models/standard-entry-class-code.md) | Optional | NACHA (the regulatory body governing the ACH network) requires that API callers (merchants, partners) obtain the consumer’s explicit authorization before initiating a transaction. To stay compliant, you’ll need to make sure that you retain a compliant authorization for each transaction that you originate to the ACH Network using this API. ACH transactions are categorized (using SEC codes) by how you capture authorization from the Receiver (the person whose bank account is being debited or credited). PayPal supports the following SEC codes.<br><br>**Default**: `StandardEntryClassCode::WEB`<br><br>**Constraints**: *Minimum Length*: `3`, *Maximum Length*: `255` | getStandardEntryClassCode(): ?string | setStandardEntryClassCode(?string standardEntryClassCode): void |
## Example (as JSON)