\n
Before going live, confirm with your Adyen contact that the paymentFacilitatorIds<\/code>, aggregatorPrefix<\/code> and amexCapnSubmitterId<\/code> are configured for your platform.<\/p>\n<\/div>\nHere is an example of a split payment request facilitated on behalf of your user:<\/p>\n
\n
<\/code-sample>\n<\/div>\nAs a payment facilitator, most payment methods allow you to facilitate ecommerce payments using an aggregated MID (your platform's scheme account), instead of requiring a MID per user.<\/p>\n
Shopper statement<\/h2>\n
When shoppers check their bank statements, they need to be able to easily identify the charges they see. The text that describes charges is known as a transaction description<\/em>, statement descriptor<\/em>, shopper statement<\/em>, or billing descriptor<\/em>. If shoppers do not recognize a transaction by its description:<\/p>\n\n- There is a higher chance your shopper issues a chargeback.<\/li>\n
- You can get a fine from the relevant card scheme related to your chargeback rate.<\/li>\n<\/ul>\n
To prevent these issues, ensure that your transaction description contains your brand or the (chain) merchant name that is most recognizable to the cardholder (as required by the card schemes), and optionally customize your transaction description.<\/p>\n
If you are not using stores in your platform, you must configure the transaction description that appears on the shopper statement. Depending on this configuration, you can additionally provide a transaction-specific shopperStatement<\/code> in your payment request. For more information, see Transaction description<\/a>.<\/p>","url":"https:\/\/docs.adyen.com\/pt\/platforms\/online-payments\/payment-facilitators","articleFields":{"description":"Learn what additional information you must send in your requests if you are a payment facilitator.","feedback_component":true,"type":"page","_expandable":{"operations":""},"status":"current","filters_component":false,"parameters":{"directoryPath":"\/platforms","model":"platform"},"next_steps":[{"title":"Split payments at authorization","description":"Learn how to split a payment at the time of authorization.","url":"\/platforms\/online-payments\/split-transactions\/split-payments-at-authorization","required":false}],"page_id":"c1fc658d-d687-41de-8096-0f9b228fb3af","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/platforms\/online-payments\/payment-facilitators","title":"Payment facilitators","content":"Card schemes require you to send certain data points with each transaction. These data points must refer to your user, who is considered the Merchant of Record when a transaction is facilitated by your platform.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nYou must have an Adyen online payments integration and a checkout UI.\n\n\nAPI credentials\nYou must have credentials for the Checkout API.\n\n\n\n\nSend user data points with a transaction\nDuring the \/sessions or \/payments authorization for each transaction, card schemes require data points that specify the following information about your user:\n\nUnique identifier: You must assign a unique identifier to each of your users.\nName: You must provide an accurate name for the user that is present on the shopper's statement. For Mastercard, this includes an aggregator prefix.\nLocation: You must provide the user's location as the location of the transaction.\n\nRequired parameters\nYou must send additionalData parameters with the \/sessions or \/payments authorization request. For cancellations, captures, and refunds, Adyen automatically populates your user's details from the initial payment.\nSubmit your request using AdditionalDataSubMerchant parameters.\n\nThe [subSellerNr] is always 1. Submit all additionalData parameters as:\nadditionalData.subMerchant.subSeller1.[parameter]\n\n\n\n\nRequired additional parameters\nDescription\n\n\n\n\n additionalData.subMerchant.numberOfSubSellers\nThe number of users in the transaction. Set this to 1.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].id\nA unique identifier you assigned to your user.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].name\nThe name of your user.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].street\nThe street name and house number of your user's address.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].postalCode\nThe postal code of your user's address, without dashes. Required only in Canada and the United States.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].city\nThe city of your user's address.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].state\nThe state code of your user's address, if applicable.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].country\nThe three-letter ISO country code of your user's address.\n\n\n additionalData.subMerchant.subSeller[subSellerNr].email\nThe email address of the user.\n\n\n\n\n additionalData.subMerchant.subSeller[subSellerNr].phoneNumber\nThe phone number of the user.\n\n\n\n\nBefore going live, confirm with your Adyen contact that the paymentFacilitatorIds, aggregatorPrefix and amexCapnSubmitterId are configured for your platform.\n\nHere is an example of a split payment request facilitated on behalf of your user:\n\n \n\nAs a payment facilitator, most payment methods allow you to facilitate ecommerce payments using an aggregated MID (your platform's scheme account), instead of requiring a MID per user.\nShopper statement\nWhen shoppers check their bank statements, they need to be able to easily identify the charges they see. The text that describes charges is known as a transaction description, statement descriptor, shopper statement, or billing descriptor. If shoppers do not recognize a transaction by its description:\n\nThere is a higher chance your shopper issues a chargeback.\nYou can get a fine from the relevant card scheme related to your chargeback rate.\n\nTo prevent these issues, ensure that your transaction description contains your brand or the (chain) merchant name that is most recognizable to the cardholder (as required by the card schemes), and optionally customize your transaction description.\nIf you are not using stores in your platform, you must configure the transaction description that appears on the shopper statement. Depending on this configuration, you can additionally provide a transaction-specific shopperStatement in your payment request. For more information, see Transaction description.","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Platforms","lvl2":"Process online payments","lvl3":"Payment facilitators"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/platforms","lvl2":"https:\/\/docs.adyen.com\/pt\/platforms\/online-payments","lvl3":"\/pt\/platforms\/online-payments\/payment-facilitators"},"levels":4,"category":"Platforms","category_color":"green","tags":["Payment","facilitators"]},"articleFiles":{"payfac-split-payment-request.js":"payfac-split-payment-request.js<\/p>"}}