{"_id":"58af1d595bedb31900382fe5","__v":0,"project":"55dd0853d2d97337001800e2","category":{"_id":"58af1bf6ebd7370f0078ba09","__v":0,"project":"55dd0853d2d97337001800e2","version":"55de36ec9067202b00de0015","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-02-23T17:29:26.972Z","from_sync":false,"order":12,"slug":"payouts","title":"Payouts"},"parentDoc":null,"user":"55dd080d0efd5821000d53b3","githubsync":"","version":{"_id":"55de36ec9067202b00de0015","__v":33,"project":"55dd0853d2d97337001800e2","createdAt":"2015-08-26T22:00:12.384Z","releaseDate":"2015-08-26T22:00:12.383Z","categories":["55de36ed9067202b00de0016","55de36ed9067202b00de0017","55de36ed9067202b00de0018","55df7dcd437b3f0d004ba204","55e4e014177b6e0d00333141","55e4e01fe252ac0d00303a99","55e4e05240cda60d003bad67","55e4e070177b6e0d00333142","55e4e0753325e60d007fbee6","55e4e0803325e60d007fbee7","55e4e086177b6e0d00333143","55e4e0a1177b6e0d00333144","55e4e0aa3325e60d007fbee8","55e4e0b140cda60d003bad6b","55e4e0bae252ac0d00303a9d","55e4e0c5177b6e0d00333145","55e4e0ee3325e60d007fbeea","55e4e0fae252ac0d00303a9e","55e4e100177b6e0d00333147","55f85c8ba3271b0d00498d55","56092e1ac5cff70d007d0131","564b64a3ee12850d0095866e","564b64b5791099170071e9ea","565cd0bfd18ae50d007183d8","565f5f5d6bafd40d0030a063","565f790d6bafd40d0030a09f","56611c464851190d003f9f5d","56637d5b7988ab0d00d0522e","56637d687988ab0d00d0522f","567835df6928b40d009dd650","56e59c043c29b117008dae5b","5704013559c5190e000ab646","572be252de40590e00026934","58af1bf6ebd7370f0078ba09","5cdad81d912ece0039e9a939"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.0.0","version":"3.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-02-23T17:35:21.213Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"PayStand's Payouts for Private Network Platforms requires all parties involved in a payout transaction to be underwritten by PayStand. For this purpose, a new customer with all the appropriate information needs to be created.\n\nThe platform customer is created by PayStand itself and its customer id and credentials will be provided to the platform's by their PayStand integration manager.\n\nBefore being able to create payouts, the platform will need to create customer accounts for each of the parties involved before it can create a payout between 2 parties. Usually this is done as part of the signup process for the platform.\n\nThe figure below depicts a very common set of interactions related to signing up for a platform and getting underwritten by PayStand. When the Platform User signs up for the Platform, as part of the Platform's business logic it can translate this signup to a PayStand customer account creation using the appropriate plan keys.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2e1e40d-SignupInteraction.png\",\n        \"SignupInteraction.png\",\n        744,\n        644,\n        \"#101010\"\n      ],\n      \"sizing\": \"full\",\n      \"caption\": \"Signup Interactions\"\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Only 1 vendor per vendor-customer per client\",\n  \"body\": \"Each client can only have 1 vendor representing a vendor customer on the private network. The platform needs to keep track of which the vendor objects it created to receive payouts on each client customer, as it is going to use the vendor id to send money too.\",\n  \"sidebar\": true\n}\n[/block]\nOnce both parties involved in a Payout are created and active, using the customer created for the vendor, the platform can create a vendor resource for the client who is going to send a payout to that vendor.","excerpt":"Platform specific business logic for Payouts","slug":"payouts-signup-implementation","type":"basic","title":"Signup Implementation"}

Signup Implementation

Platform specific business logic for Payouts

PayStand's Payouts for Private Network Platforms requires all parties involved in a payout transaction to be underwritten by PayStand. For this purpose, a new customer with all the appropriate information needs to be created. The platform customer is created by PayStand itself and its customer id and credentials will be provided to the platform's by their PayStand integration manager. Before being able to create payouts, the platform will need to create customer accounts for each of the parties involved before it can create a payout between 2 parties. Usually this is done as part of the signup process for the platform. The figure below depicts a very common set of interactions related to signing up for a platform and getting underwritten by PayStand. When the Platform User signs up for the Platform, as part of the Platform's business logic it can translate this signup to a PayStand customer account creation using the appropriate plan keys. [block:image] { "images": [ { "image": [ "https://files.readme.io/2e1e40d-SignupInteraction.png", "SignupInteraction.png", 744, 644, "#101010" ], "sizing": "full", "caption": "Signup Interactions" } ] } [/block] [block:callout] { "type": "warning", "title": "Only 1 vendor per vendor-customer per client", "body": "Each client can only have 1 vendor representing a vendor customer on the private network. The platform needs to keep track of which the vendor objects it created to receive payouts on each client customer, as it is going to use the vendor id to send money too.", "sidebar": true } [/block] Once both parties involved in a Payout are created and active, using the customer created for the vendor, the platform can create a vendor resource for the client who is going to send a payout to that vendor.