Visa Direct - Purpose of payment #188
Conversation
cbobach
left a comment
cbobach
left a comment
There was a problem hiding this comment.
I think we need to highlight that these are only Visa specific fields, know that you specify the naming of the document.
I'm not sure which parts/information we normally put in the Partner Guideline and which we add here, but think information in the line of these is not something we have added to the api-docs previously 🤷
website/content/gateway/api_reference/resources/credits/credits.md
Outdated
Show resolved
Hide resolved
| {{% description_term %}}purpose_of_payment {{% regex %}}[A-Z]{6}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}} The fields code shall reflect the nature and purpose of the transaction. | ||
| Valid codes are list in Visas Purpose of Payment - Standardized Codes List. | ||
| {{% regex_optional %}} Required for Visa cross-border transactions destined for Argentina, Bangladesh, Chile, Columbia, Egypt, India and Mexico. {{% /regex_optional %}} |
There was a problem hiding this comment.
| {{% regex_optional %}} Required for Visa cross-border transactions destined for Argentina, Bangladesh, Chile, Columbia, Egypt, India and Mexico. {{% /regex_optional %}} | |
| {{% regex_optional %}}Required for Visa cross-border transactions destined for some specific countries; otherwise optional. See the partner guideline for details.{{% /regex_optional %}} |
Maybe? 😬
| {{% regex_optional %}}Required if the merchant account's Business Application Identifier (BAI) is Funds Disbursement (FD).{{% /regex_optional %}} | ||
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}recipient[purpose_of_payment] {{% regex %}}[A-Z]{6}{{% /regex %}}{{% /description_term %}} |
There was a problem hiding this comment.
Purpose of Payment is not related to recipient data so it does not make sense to have it in the recipient dictionary.
AFAICT, we should the same as for credits, i.e. have it on the same level as e.g. text_on_statement. Because the Debits section currently only refers to the parameters for an authorization, we need to add a Parameters section to debits, stating that these parameters are in addition to the parameters supported for an authorization.
| {{% /description_details %}} | ||
|
|
||
| {{% description_term %}}purpose_of_payment {{% regex %}}[A-Z]{6}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}} The fields code shall reflect the nature and purpose of the transaction. |
There was a problem hiding this comment.
| {{% description_details %}} The fields code shall reflect the nature and purpose of the transaction. | |
| {{% description_details %}}The fields code shall reflect the nature and purpose of the transaction. |
IMHO we should try to converge towards not having these purposeless spaces 🙂
|
|
||
| {{% description_term %}}purpose_of_payment {{% regex %}}[A-Z]{6}{{% /regex %}}{{% /description_term %}} | ||
| {{% description_details %}} The fields code shall reflect the nature and purpose of the transaction. | ||
| Valid codes are list in Visas Purpose of Payment - Standardized Codes List. |
There was a problem hiding this comment.
| Valid codes are list in Visas Purpose of Payment - Standardized Codes List. | |
| Valid codes are list in Visa's Purpose of Payment - Standardized Codes List. |
As a part of: https://github.com/clearhaus/issues-project-management/issues/264
Visa requires Purpose of payment on both AFT and OCT for cross-border transactions.
Based on
Visas Purpose of Payment - Standardized Codes ListI can only see 6 character codes in the list.