...
To customize the descriptor
...
shown on a Merchant Disbursement
...
, Referrers can choose to add a Secondary
...
Descriptor
...
to a Merchant entity or
...
their payout/withdrawal schedule. This
...
feature allows Referrers to have their name displayed on their Merchant Disbursements and helps merchants with multiple locations differentiate between disbursements. By incorporating this Secondary Descriptor at the end of the Disbursement Descriptor (before the Merchant Name)
...
, this personalized option assists merchants in easily recognizing their disbursements, enhancing the transparency and structure of financial transactions.
| Info |
|---|
Secondary Descriptors are limited to Worldpay/Vantiv Merchant Funding. |
Default Disbursement Descriptors:
...
The Secondary Descriptor will append at the end of the Default Merchant Disbursement Descriptor (before the Merchant Name) and is limited to 15 characters. The display of the descriptor can vary slightly per each issuing bank.
MerchPayout SV9T 8447752748 000000 {Merchant Name}
MerchPayout SV93 8447752748 000000 {Merchant Name}
The Secondary Payout Descriptor will append at the end of the Default Merchant Disbursement Descriptor (before the Merchant Name) and is limited to 15 characters.
Use Cases
Referrers that want their name to appear on their Merchant Disbursements.
Merchants with multiple locations that want to differentiate disbursements from Payrix.
...
| Note |
|---|
Warning: This Descriptor is specific to Merchant Disbursements (Funding Files) and not represented on the Cardholder statement. The cardholder statement descriptor is based on the Entity DBA or Entity Legal Name if DBA is not provided. |
Enabling a Secondary
...
Descriptor via Portal:
You can utilize Secondary
...
Descriptors for individual Merchants by visiting their Account Overview Menu. See the steps below:
| Note |
|---|
Note: A Secondary Payout Descriptor can be set up on a merchant entity only |
...
Add a Secondary Payout Descriptor in the Merchant Account Overview
Step 1
...
: From the Dashboard, click Merchants from the side menu
...
. Then select a Merchant to access its Profile page.
Step 2
...
: Choose a Merchant you wish to add the Secondary
...
Descriptor to.
...
Step 3
...
: Scroll select and edit the Secondary
...
Descriptor field:
...
...
Add a Secondary
...
Descriptor in the Merchant Withdrawals Menu
| Note |
|---|
...
Warning: A Secondary Descriptor |
...
set from the Withdrawals menu will override the Secondary Payout Descriptor value set from the Merchant Overview menu. |
Step 1
...
: From the
...
Merchant Profile, click
...
Withdrawals from the
...
left-hand menu.
...
Step 2
...
Choose a Merchant to which you wish to add the Secondary Payout Descriptor and click the “login view” button on the right-hand column.
...
Step 3
Click Withdrawals under Payments in the Menu bar, and locate a scheduled withdrawal:
...
Step 4
...
: Click the active Withdrawal Schedule(s) listed for the Merchant.
Step 3: Click the edit icon in the upper right
...
corner, then add the descriptor under the Secondary Descriptor field.
Step 4: Click the confirm icon to save the changes.
Result: This Secondary Descriptor field will be automatically assigned to all future payouts (withdrawals) for that Merchant
...
.
...
Enabling a Secondary
...
Descriptor via API:
A Secondary
...
Descriptor can be set up on a merchant entity, payout/withdrawal flow, or a payout/withdrawal schedule.
If a Secondary
...
Descriptor is not set up on a Payout/Withdrawal Schedule then it will be pulled from the entity (if applicable).
Entity Secondary
...
Descriptor
By setting up a Secondary
...
Descriptor on an entity it will appear for all their disbursements regardless of the payout/withdrawal schedule.
| Info |
|---|
If a payout has a Secondary |
...
Descriptor set then this will override the Secondary |
...
Descriptor setup on the entity (if applicable). |
This can be added to an entity upon creation or via an update via the entities.payoutSecondaryDescritptor field.
Create a Merchant Entity with Secondary
...
Descriptor:
POST /entities
| Code Block |
|---|
{
"type": 2,
"name": "Entity Name",
"address1": "Address 1",
"address2": null,
"city": "City",
"state": "State",
"zip": "00000",
"country": "USA",
"phone": "8888888888",
"fax": null,
"email": "Entity.Email@gmail.com",
"payoutSecondaryDescriptor": "Secondary |
...
Descriptor",
"ein": "123456789",
"website": "http:// |
...
example.com", "tcVersion": "3.0", "tcAcceptDate": "202012111528", "tcAcceptIp": "", "currency": "USD", } |
Create a Payout/Withdrawal Secondary
...
Descriptor
A Secondary
...
Descriptor can be set up on a Payout/Withdrawal schedule so that any disbursement created as part of that schedule has a unique Secondary
...
Descriptor appended.
This can be added to a Payout/Withdrawal upon creation or via an update to the payouts.secondaryDescriptor field.
Create Merchant Payout/Withdrawal with Secondary
...
Descriptor:
POST /payouts
| Code Block |
|---|
{
"entity": "p1_ent_ID",
"account": "{account token}",
"name": "Payout Name",
"amount": "100",
"schedule": "5",
"secondaryDescriptor": "Secondary |
...
Descriptor"
"start" : "20201211",
"um": 2
}
|
Example Secondary
...
Descriptor:
MerchPayout SV9T 8447752748 000000 Secondary
...
Descriptor {Merchant Name}
...