Key Points

1. BICARSA
2. dependencies on identities ( organizations, individuals ), accounts, accounting systems
3. payments
4. credit payments
5. bank payments
6. settlements
7. orders
8. invoicing
9. receivables
10. sales analysis

References

Payments Task List

Key Product Solution Questions

1. What are the payment scenarios in F2P Finance?
2. what are the challenges, opportunities for each stage and role in the payment chain?
3. who can pay for the solution in the payment chain?  ( NOT the growers )
4. what's the F2P story we share?   ( challenges & opportunities,  F2P FBRs, case studies )

Product Delivery Concepts 

Key Payment Services Concepts

DPS - Digital Payment Services Feature Concepts 

--------------
#DPS - digital payment services - DPS
--------------

- buy payment tokens with ACH funds or credit card
- cash out payment tokens to ACH account
- send money from ACH account to ACH account
- convert currency on transfers

scenarios ?
- any including international payments, remittances
- supports many currency conversions
- low cost
- fast

DPS considerations
- which services to use ( Stellar, Wise, Stripe or ?)
- secure payment models
- secure sharing of bank accounts
- standard or custom payment use cases
- related contract methods for payments
- related contract documents
- digital signatures
- wallets
- supported identity types, verifications for accounts
- interoperability on identities
- interoperability on wallets
- interoperability on services ( DID methods etc )
- support for terms verifications
- support for escrow payments
- support for reverse payments on escrow failures

DPS fees
- different use cases may have different fees
- fee structures should allow multiple servicers
- fee structures should support discount methods applied by account, account type ( eg a flat fee for all trans in period)
- fee visibility restricted by role
- should include coverage of all related costs to run, maintain, manage DPS
- should support usage credits, tokens based on defined rules

Thomas POC features tested 

buy tokens with credit card

add payment method for account
buy tokens on credit card
show token purchase
explorer - view new account balance minus fees
stripe login
stripe payment with credit card shown

cash payout using xwise

xwise summary screen
xwise login - MFA
add new bank account
create cash payout
confirm the payout request w transfer shown
Stellar explorer shows payout transaction on xwise
> consider login to view the JSON details
xwise shows the payout to Paramount and the $1.05 fee

send money feature

F2P Solution Concepts 

F2P Modules ( needs review )

IAMS - Identity, Access and Memberships Services

SCM - Supply Chain Management 

FMS - Financial Management Services 

Invoicing

Invoice reconciliation

Invoice payments

Direct payments on delivery

Contract payments 

Invoice Loans - Factoring receivables

Crop Loans - highly risky

Payments - via payment services

Receivables 

Purchasing

General Ledger

Payroll

External integrations

Analytics

food supply chain logistics improvement

food safety 

ethical sourcing

fresher food

F2P Incomm presentation deck

Deck for InComm - Sep 23 v2 .pptx

see the ps deck model ...

https://en.wikipedia.org/wiki/GS1

context - existing solution

use cases for scope
quality - efficiency
security - safety
consent mgt
transparency
trust - immutability - traceability
integrations

problem stmts
current system focus ( add roadmap )
from user journeys ( cpa, dmv, dbr, firms )

user full credential exposure for proof requests
user id, pwd risks, issues
state reduced fraud, disputes

new system

impacts for use cases
food recall reduction w data quality, automation, immutability,
transparency

strategy
add did, credentials for ssi, pii

impacts
security
data protection
data privacy
easy secure access
consent mgt
reduced fraud, impersonation

any specific kpis / metrics to measure impacts?
any other related references on benefits ?
how decentralized a network is this?

next to last slide ( F2P ) shows
safety benefit ( food recall )

no other slides show the sourcing or produce quality benefits

revenue slide could benefit from added text to clarify the model

recommendations
strategies
implementations
decisions
next steps

appendices

related stds - ssi, did, toip, pki, ...
swt id bc pptx

Potential Value Opportunities

Food Supply Chain

Distribution models ??

free 30 day trials hosted

limited function, capacity open-source version

enterprise version

Potential Differentiators ??

pluggable interfaces for:  identities, RBAC, data models, logic scripts, workflows, events

industry specific

pre-built integrations - EDI etc

partners on sub-systems - eg payments, inventory

Research list

Normal ERP logistics apps in cloud

Other Trade Finance solutions and use cases

https://www.finastra.com/solutions/transaction-banking/trade-supply-chain-finance

Bills of Lading

Tokenizing Bills of Lading - https://www.youtube.com/watch?v=JN69tm9bq7c

Potential Challenges

Legal Terms and Documents 

I have shared the legal artifacts on Blockchain and would appreciate your views.This will help our attorney draft the contents precisely matching our expectations.

​My Onboarding support concepts

good customer service

easy, effective, low-cost Paramount support options

• No-charge Account planning meetings to define

  • goals, expected usage, gather requirements, plan any custom services, standard onboarding, training, connections, support and more

• use youtube videos, docs as an option here

• use knowledge base with youtube video links as first stop for help normally

• provide direct email, live chat and phone support options for registered account contacts

• use custom Zoom support meetings as needed to resolve issues

• use online Grails app to record and manage work requests ( problems, questions, feature requests )

• use online BIRT or equivalent Web report tool to show system usage and manage work request status

• customer portal provides account information and billing status

​Customer responsibilities for implementation and support

• Customer Resources committed to meet planned onboarding and support requirements

• Customer designates specific support contacts who go through on-boarding training courses

• Customer is responsible for integrations to existing systems unless Paramount hired on a custom SOW under an MDA to provide services integrations

• Customer documents planned usage of services using JEPL ( Java Event Processing Language ) to define a planned usage model for workflows, event notifications, automation

• Paramount provides support on usage documentation with JEPL via knowledge base and support staff

• Customer provides a test environment to test and validate planned usage and identity support problems separate from Production systems

• Customer uses Paramount online support templates to record any support incidents ( problems, questions, feature requests ) and submit to Paramount online ( see work request template as a Grails app )

Candidate Solutions

F2P solution

MVP Plan

https://drive.google.com/file/d/1fmNi3Nptr335LZyp-40l8sM7kntZLzFh/view?usp=sharing

OKR - Objectives Key Results 

Problem Statements 

https://paramountsoft.atlassian.net/wiki/spaces/FAR/pages/264077353/Problem+Statements

Meetings

Restructure F2P product plan - 210504

Step-by-step guide for Example

sample code block

Recommended Next Steps

Related articles