Enter Delivery Mechanism Information Fields

This section details each of the fields that are available when Setting Up a Delivery Mechanism in the Create new delivery mechanism page. It details what you can enter for each field, and provides examples of the data you should enter when creating a delivery mechanism.

The user interface and fields available will change depending on the token type you select. The fields available for each token type are listed below.

Bank account token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type)(Mandatory): Select the token you want to use for the delivery mechanism.
3. Token number pattern: <add explanation>
4. Modality(Mandatory): Select the modality you want to use for the delivery mechanism.
5. Description: Enter a description of the delivery mechanism.
6. Financial Service Provider representative : Select the SCOPE user designated as the representative of the Financial Service Provider. The representative must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

7. PIN codes managers: Select the SCOPE user(s) designated to download PIN codes for printed SCOPE Smart cards. The user(s) must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

8. Programme Officer : Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

9. PIN code delivery confirmation : Click the check box if the delivery mechanism requires PIN code delivery confirmation.
10. Card delivery confirmation : Click the checkbox if the delivery mechanism requires card delivery confirmation.
11. Sub Wallets: <add explanation>
12. Transfer charge: <add explanation>

Managing the Registry Statement and PAF

When setting up a delivery mechanism with the bank account token type, you can specify the rows you want to appear in the Registry Statement and Payment Advice File (PAFPayment Advice File).

To specify the rows you want to appear, perform the following steps:

1. In the Create new delivery mechanism page, click Registry Statement or Payment Advice File.

   

2. In the File Headers window, edit the rows you want to appear in the Registry Statement or PAFPayment Advice File.

   • Click and hold the move icon () to drag and drop the row to change the order of the rows.

     

   • Click the delete icon () to delete rows.

     

   • Click Add another row? to add new rows.

     

3. Click Apply to save changes to the rows.

   

Managing the transfer charge

When setting up a delivery mechanism with the bank account token type, you can define any transaction charges that the beneficiary should be charged for cash transfers.

To define any transaction charges, perform the following steps:

1. In the Create new delivery mechanism page, enter the relevant values into the Maximum transfer and Transaction feefields.

   

2. Click add charge to add any additional charges.

   

Mobile number token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type)(Mandatory): Select the token you want to use for the delivery mechanism.
3. Token number pattern: <add explanation>
4. Modality (Mandatory): Select the modality you want to use for the delivery mechanism.
5. Description: Enter a description of the delivery mechanism.
6. Financial Service Provider representative : Select the SCOPE user designated as the representative of the Financial Service Provider. The representative must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

7. Programme Officer: Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

8. Payment Advice File template: <add explanation>
9. Transfer charge: <add explanation>

Managing the Registry Statement and PAF

When setting up a delivery mechanism with the mobile number token type, you can specify the rows you want to appear in the Registry Statement and Payment Advice File (PAFPayment Advice File).

To specify the rows you want to appear, perform the following steps:

1. In the Create new delivery mechanism page, click Registry Statement or Payment Advice File.

   

2. In the File Headers window, edit the rows you want to appear in the Registry Statement or PAFPayment Advice File.

   • Click and hold the move icon () to drag and drop the row to change the order of the rows.

     

   • Click the delete icon () to delete rows.

     

   • Click Add another row? to add new rows.

     

3. Click Apply to save changes to the rows.

   

Managing the transfer charge

When setting up a delivery mechanism with the mobile number token type, you can define any transaction charges that the beneficiary should be charged for cash transfers.

To define any transaction charges, perform the following steps:

1. In the Create new delivery mechanism page, enter the relevant values into the Maximum transfer and Transaction feefields.

   

2. Click add charge to add any additional charges.

   

Building blocks token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type)(Mandatory): Select the token you want to use for the delivery mechanism.
3. Token number pattern: <add explanation>
4. Modality (Mandatory): Select the modality you want to use for the delivery mechanism.
5. Description: Enter a description of the delivery mechanism.
6. Building Blocks endpoint URL: <add explanation>
7. Building Blocks API Token: <add explanation>
8. Number of Retries: <add explanation>
9. Enable sending SMS updates?: Click the check box to enable building blocks to send SMS updates.
10. Financial Service Provider representative : Select the SCOPE user designated as the representative of the Financial Service Provider. The representative must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

11. Programme Officer: Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

Managing the Registry Statement

When setting up a delivery mechanism with the building blocks token type, you can specify the rows you want to appear in the Registry Statement.

To specify the rows you want to appear, perform the following steps:

1. In the Create new delivery mechanism page, click Registry Statement.

   

2. In the File Headers window, edit the rows you want to appear in the Registry Statement or PAFPayment Advice File.

   • Click and hold the move icon () to drag and drop the row to change the order of the rows.

     

   • Click the delete icon () to delete rows.

     

   • Click Add another row? to add new rows.

     

3. Click Apply to save changes to the rows.

   

SCOPE CARD token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type)(Mandatory): Select the token you want to use for the delivery mechanism.
3. Modality(Mandatory): Select the modality you want to use for the delivery mechanism.
4. Description: Enter a description of the delivery mechanism.
5. Fingerprint Verification Required: Click the checkbox to enable fingerprint verification when using mPOS terminals.
6. PIN Code Verification Required: Click the checkbox to enable PIN code verification when using mPOS terminals.

7. PIN codes managers: Select the SCOPE user(s) designated to download PIN codes for printed SCOPE Smart cards. The user(s) must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

8. Programme Officer: Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

9. Card design: Select the card design you want to use from the drop-down menu.
10. Print transaction value on receipt: Click the checkbox to print the transaction value on the receipt when using commodity vouchers at mPOS terminals.

WFP barcode-ID card token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type)(Mandatory): Select the token you want to use for the delivery mechanism.
3. Modality(Mandatory): Select the modality you want to use for the delivery mechanism.
4. Description: Enter a description of the delivery mechanism.
5. Fingerprint Verification Required : Click the checkbox to enable fingerprint verification when using mPOS terminals.
6. PIN Code Verification Required : Click the checkbox to enable PIN code verification when using mPOS terminals.

7. Programme Officer: Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

8. Card design: Select the card design you want to use from the drop-down menu.

Barcode card token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type) (Mandatory): Select the token you want to use for the delivery mechanism.
3. Modality (Mandatory): Select the modality you want to use for the delivery mechanism.
4. Description: Enter a description of the delivery mechanism.
5. Fingerprint Verification Required: Click the checkbox to enable fingerprint verification when using mPOS terminals.
6. PIN Code Verification Required: Click the checkbox to enable PIN code verification when using mPOS terminals.
7. Share household name on voucher: <add explanation>

8. Programme Officer: Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

9. Card design: Select the card design you want to use from the drop-down menu.

Kifiya SMS or paper voucher token

1. Name(Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type)(Mandatory): Select the token you want to use for the delivery mechanism.
3. Modality(Mandatory): Select the modality you want to use for the delivery mechanism.
4. Description: Enter a description of the delivery mechanism.

5. Programme Officer: Select the SCOPE user designated as the Programme Officer. The user must already have a SCOPE user account set up for them. For more information, see Assigning User Roles.

Paper voucher token

1. Name (Mandatory): Enter the name of the delivery mechanism.
2. Token / Mean (token type) (Mandatory): Select the token you want to use for the delivery mechanism.
3. Description: Enter a description of the delivery mechanism.

Examples

In this example, we create a delivery mechanism for direct cash.

Field	Value	Notes
Name	Cash transfer
Token / Mean (token type)	Bank account
Token number pattern	<add example>
Modality	Direct cash
Description	A delivery mechanism for transferring cash to beneficiaries.
Financial Service Provider representative	<add example>
PIN codes managers	<add example>
Programme Officer	<add example>
PIN code delivery confirmation	Not required	The checkbox was not clicked.
Card delivery confirmation	Not required	The checkbox was not clicked.
Sub Wallets	<add example>
Transfer charge	<add example>