Stripe: Customer, Create<\/div>
Creates a Customer object on the payment platform Stripe. Customer objects allow you to perform recurring charges. Note that it is necessary to implement tokenization mechanism that directly interacts with the customer browser and Stripe in advance.<\/div><\/div>\n\n\n
<\/span>Configs<\/div>
\n
- \n
- <\/i><\/span> U: Select HTTP_Authz Setting *<\/span><\/li>\n
- <\/i><\/span> B: Set Token *<\/span>#{EL}<\/sup><\/span><\/li>\n
- <\/i><\/span> C1: Set Customer Email *<\/span>#{EL}<\/sup><\/span><\/li>\n
- <\/i><\/span> C2: Set Customer Description (Registration Num, Corp Name, etc) *<\/span>#{EL}<\/sup><\/span><\/li>\n
- <\/i><\/span> C3: Set Customer Name (Contact Name, Trade Name, etc)#{EL}<\/sup><\/span><\/li>\n
- <\/i><\/span> D1: Select STRING DATA for Stripe Customer ID (update) *<\/span><\/li>\n
- <\/i><\/span> D2: Select STRING DATA for Card Brand (update)<\/li>\n
- <\/i><\/span> D3: Select STRING DATA for Card Last4 (update)<\/li>\n
- <\/i><\/span> D4: Select STRING\/YMDATE for Card Exp (update)<\/li>\n<\/ul>\n<\/div><\/div>\n\n\n
<\/span>Script (click to open)<\/div>\n\n\n\n\/\/ GraalJS Script (engine type: 2)\n\n\/\/\/\/\/\/\/\/ START "main()" \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\n\nmain();\nfunction main(){ \n\n\/\/\/\/ == Config Retrieving \/ \u5de5\u7a0b\u30b3\u30f3\u30d5\u30a3\u30b0\u306e\u53c2\u7167 ==\nconst strAuthzSetting = configs.get ( "AuthzConfU" ); \/\/\/ REQUIRED\n engine.log( " AutomatedTask Config: Authz Setting: " + strAuthzSetting );\nconst strTokenId = configs.get( "strSetConfB" ); \/\/ required\nconst strCustomerEmail = configs.get( "strSetConfC1" ); \/\/ required\nconst strCustomerDescr = configs.get( "strSetConfC2" ); \/\/ required\nconst strCustomerName = configs.get( "strSetConfC3" ); \/\/ not\nconst pocketCustomerId = configs.getObject( "SelectConfD1" ); \/\/ required\nconst pocketCardBrand = configs.getObject( "SelectConfD2" ); \/\/ not\nconst pocketCardLast4 = configs.getObject( "SelectConfD3" ); \/\/ not\nconst pocketCardExp = configs.getObject( "SelectConfD4" ); \/\/ not *STRING\/YMDATE\n\nif( strTokenId === "" ){\n throw new Error( "\\n AutomatedTask ConfigError:" +\n " Config {Token ID B} is empty \\n" );\n}\nif( strCustomerEmail === "" ){\n throw new Error( "\\n AutomatedTask ConfigError:" +\n " Config {CustomerEmail C1} is empty \\n" );\n}\nif( strCustomerDescr === "" ){\n throw new Error( "\\n AutomatedTask ConfigError:" +\n " Config {CustomerDescription C2} is empty \\n" );\n}\n\n\n\/\/\/\/ == Data Retrieving \/ \u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u30c7\u30fc\u30bf\u306e\u53c2\u7167 ==\n\/\/ (nothing, except Expression Language config)\n\n\n\/\/\/\/ == Calculating \/ \u6f14\u7b97 ==\n\/\/\/ POST \/v1\/customers\n\/\/ https:\/\/stripe.com\/docs\/api\/customers\/create\n\/\/ https:\/\/stripe.com\/docs\/api\/authentication\n\/\/ If you need to authenticate via bearer auth (e.g., for a cross-origin request), \n\/\/ use -H "Authorization: Bearer sk_xxx" instead of -u sk_test_xxx.\n\n\/\/ preparing for API Request\nlet apiUri = "https:\/\/api.stripe.com\/v1\/customers";\nlet apiRequest = httpClient.begin(); \/\/ HttpRequestWrapper\n apiRequest = apiRequest.authSetting( strAuthzSetting ); \/\/ with "Authorization: Bearer XX"\n \/\/ https:\/\/questetra.zendesk.com\/hc\/en-us\/articles\/360024574471-R2300#HttpRequestWrapper\n apiRequest = apiRequest.formParam( "source", strTokenId );\n apiRequest = apiRequest.formParam( "email", strCustomerEmail );\n apiRequest = apiRequest.formParam( "description", strCustomerDescr );\n apiRequest = apiRequest.formParam( "name", strCustomerName );\n\n\/\/ throwing Request to the API (POST, GET, PUT, etc)\nengine.log( " AutomatedTask Trying: POST " + apiUri );\nconst response = apiRequest.post( apiUri );\nconst responseCode = response.getStatusCode() + "";\nengine.log( " AutomatedTask ApiResponse: Status " + responseCode );\nif( responseCode !== "200"){\n throw new Error( "\\n AutomatedTask UnexpectedResponseError: " +\n responseCode + "\\n" + response.getResponseAsString() + "\\n" );\n} \/\/ C.F. https:\/\/stripe.com\/docs\/api\/errors\n\n\/\/ parsing Response Json\nconst responseStr = response.getResponseAsString() + "";\n\/\/engine.log( " DEBUG for api upgrade: \\n" + responseStr );\nconst responseObj = JSON.parse( responseStr );\nengine.log( " AutomatedTask ApiResponse:" +\n " New CustomerObject ID: " + responseObj.id );\nengine.log( " AutomatedTask ApiResponse:" +\n " Card Brand: " + responseObj.sources.data[0].brand );\n\n\n\/\/\/\/ == Data Updating \/ \u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u30c7\u30fc\u30bf\u3078\u306e\u4ee3\u5165 ==\nengine.setData( pocketCustomerId, responseObj.id );\nif( pocketCardBrand !== null ){ \/\/ STRING\n engine.setData( pocketCardBrand, responseObj.sources.data[0].brand );\n}\nif( pocketCardLast4 !== null ){ \/\/ STRING\n engine.setData( pocketCardLast4, responseObj.sources.data[0].last4 );\n}\nif( pocketCardExp !== null ){ \/\/ STRING or YMDATE\n if( pocketCardExp.matchDataType( "STRING" ) ){\n engine.setData( pocketCardExp, \n ("0" + responseObj.sources.data[0].exp_month).slice(-2) + "\/" +\n responseObj.sources.data[0].exp_year );\n }else{\n engine.setData( pocketCardExp, \n java.sql.Date.valueOf(\n responseObj.sources.data[0].exp_year + "-" +\n ("0" + responseObj.sources.data[0].exp_month).slice(-2) + "-01"\n )\n );\n }\n}\n\n} \/\/\/\/\/\/\/\/ END "main()" \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\n\n\/*\nNotes:\n- Create a "Customer object" on Stripe using Token.\n - An environment for recurring charges will be built on Stripe.\n - Eg. place it after the "Payment card registration" step in the order handling workflow.\n- A Tokenization mechanism (card registration form) is required.\n - Refer to the sample below for how to implement the card registration form (tokenization).\n - "Elements" (custom payment forms)\n - https:\/\/stripe.com\/docs\/stripe-js\n - https:\/\/support.questetra.com\/tips\/form-decoration-examples\/#tokenize\n - "Checkout" (forms hosted on Stripe)\n - https:\/\/stripe.com\/docs\/payments\/checkout\n- Use the customer object ID (CustomerID) for flat-rate billing and usage billing.\n - Can be obtained in this creation process. Example "cus_XXXXXYYYYYZZZZ"\n\nNotes(ja):\n- Token \u3092\u5229\u7528\u3057\u3066 Stripe \u4e0a\u306b "\u9867\u5ba2\u30aa\u30d6\u30b8\u30a7\u30af\u30c8" \u3092\u751f\u6210\u3057\u307e\u3059\u3002\n - Stripe\u4e0a\u306b\u300c\u7d99\u7d9a\u7684\u306a\u8ab2\u91d1\u3092\u5b9f\u73fe\u3059\u308b\u305f\u3081\u306e\u74b0\u5883\u300d\u304c\u69cb\u7bc9\u3055\u308c\u307e\u3059\u3002\n - \u305f\u3068\u3048\u3070\u3001\u53d7\u6ce8\u5bfe\u5fdc\u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u306b\u304a\u3051\u308b\u300c\u6c7a\u6e08\u30ab\u30fc\u30c9\u306e\u767b\u9332\u300d\u306e\u5de5\u7a0b\u306e\u76f4\u5f8c\u306b\u914d\u7f6e\u3057\u307e\u3059\u3002\n- Token \u5316\u306e\u4ed5\u7d44\u307f\uff08\u30ab\u30fc\u30c9\u767b\u9332\u30d5\u30a9\u30fc\u30e0\uff09\u304c\u5225\u9014\u5fc5\u8981\u3067\u3059\u3002\n - \u30ab\u30fc\u30c9\u767b\u9332\u30d5\u30a9\u30fc\u30e0\uff08\u30c8\u30fc\u30af\u30f3\u5316\uff09\u306e\u5b9f\u88c5\u65b9\u6cd5\u306f\u4ee5\u4e0b\u306e\u30b5\u30f3\u30d7\u30eb\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002\n - "Elements" (custom payment forms)\n - https:\/\/stripe.com\/docs\/stripe-js\n - https:\/\/support.questetra.com\/ja\/tips\/form-decoration-examples\/#tokenize\n - "Checkout" (forms hosted on Stripe)\n - https:\/\/stripe.com\/docs\/payments\/checkout\n- \u5b9a\u984d\u8ab2\u91d1\u3084\u5229\u7528\u91cf\u8ab2\u91d1\u306e\u969b\u306b\u306f\u3001\u9867\u5ba2\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306eID\uff08CustomerID\uff09\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002\n - \u751f\u6210\u5de5\u7a0b\u3067\u53d6\u5f97\u53ef\u80fd\u3067\u3059\u3002 \u4f8b "cus_XXXXXYYYYYZZZZ"\n\nAPPENDIX\n- PCI DSS Compliance (SAQ A) is to ensure that payment card data never touches any server.\n - https:\/\/stripe.com\/docs\/security\/guide\n - This automated step allows you to build a system that does not retain sensitive info with no-code.\n- Set Stripe SecretKey in "HTTP Authentication" > "Token Fixed Value"\n -"sk_live_XXXXXyyyyyZZZZZxxxxxYYYY" (32 letters)\n- For the contents of the error code (ResponseCode other than 200)\n - https:\/\/stripe.com\/docs\/api\/errors\n- When migrating from the old version (2020-06-03), add a new one instead of updating.\n - The method of setting SecretKey has changed. (To be hidden)\n - https:\/\/support.questetra.com\/addons\/stripe-customer-object-create\/\n - Add a new Addon to the workflow app (Maage Add-on > Definition of Service task > Add)\n - Added "Token Fixed Value" at "HTTP Authz Settings"\n - In the modeler, place the new version of the add-on and remove the old version of the add-on.\n - Release workflow app.\n\nAPPENDIX-ja\n- PCI DSS \u300c\u30ab\u30fc\u30c9\u60c5\u5831\u306e\u975e\u4fdd\u6301\u300d(SAQ A)\u306b\u306f\u3001\u30ab\u30fc\u30c9\u60c5\u5831\u306f\u3044\u304b\u306a\u308b\u30b5\u30fc\u30d0\u3082\u7d4c\u7531\u3057\u3066\u306f\u3044\u3051\u307e\u305b\u3093\u3002\n - https:\/\/stripe.com\/docs\/security\/guide\n - \u3053\u306e\u81ea\u52d5\u5de5\u7a0b\u3092\u6d3b\u7528\u3059\u308c\u3070\u3001\u30bb\u30f3\u30b7\u30c6\u30a3\u30d6\u60c5\u5831\u3092\u4fdd\u6301\u3057\u306a\u3044\u4ed5\u7d44\u307f\uff08\u5b8c\u5168\u59d4\u8a17\uff09\u3092\u30ce\u30fc\u30b3\u30fc\u30c9\u958b\u767a\u3067\u304d\u307e\u3059\u3002\n- Stripe SecretKey \u306f "HTTP\u8a8d\u8a3c\u8a2d\u5b9a" \uff1e "\u30c8\u30fc\u30af\u30f3\u76f4\u63a5\u6307\u5b9a" \u306b\u3066\u30bb\u30c3\u30c8\u3057\u3066\u304f\u3060\u3055\u3044\n - "sk_live_XXXXXyyyyyZZZZZxxxxxYYYY" (32\u6587\u5b57)\n- \u30a8\u30e9\u30fc\u30b3\u30fc\u30c9\uff08200\u4ee5\u5916\u306eResponseCode\uff09\u306e\u5185\u5bb9\u306b\u3064\u3044\u3066\u306f\u4ee5\u4e0b\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002\n - https:\/\/stripe.com\/docs\/api\/errors\n- \u65e7\u7248(2020-06-03)\u304b\u3089\u79fb\u884c\u3059\u308b\u5834\u5408\u3001\u66f4\u65b0\u3067\u306f\u306a\u304f\u3001\u65b0\u898f\u306b\u8ffd\u52a0\u3057\u3066\u304f\u3060\u3055\u3044\u3002\n - SecretKey \u306e\u8a2d\u5b9a\u65b9\u6cd5\u304c\u5909\u66f4\u3055\u308c\u3066\u3044\u307e\u3059\u3002\uff08\u96a0\u853d\u5316\uff09\n - https:\/\/support.questetra.com\/ja\/addons\/stripe-customer-object-create\/\n - \u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u30a2\u30d7\u30ea\u306b\u3001\u65b0\u3057\u3044Addon\u3092\u8ffd\u52a0 \uff08\u30a2\u30c9\u30aa\u30f3\u306e\u7ba1\u7406 \uff1e \u30b5\u30fc\u30d3\u30b9\u30bf\u30b9\u30af\u5b9a\u7fa9\u30d5\u30a1\u30a4\u30eb \uff1e \u8ffd\u52a0\uff09\n - "HTTP\u8a8d\u8a3c\u8a2d\u5b9a" \u304b\u3089 "\u30c8\u30fc\u30af\u30f3\u76f4\u63a5\u6307\u5b9a" \u3092\u8ffd\u52a0\n - \u30e2\u30c7\u30e9\u3067\u3001\u65b0\u7248\u306e\u30a2\u30c9\u30aa\u30f3\u3092\u914d\u7f6e\u3057\u3001\u65e7\u7248\u306e\u30a2\u30c9\u30aa\u30f3\u3092\u524a\u9664\n - \u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u30a2\u30d7\u30ea\u3092\u30d0\u30fc\u30b8\u30e7\u30f3\u30a2\u30c3\u30d7\uff08\u30ea\u30ea\u30fc\u30b9\uff09\n*\/\n\n<\/code><\/pre><\/div>\n\n\n<\/div><\/div>\n\n\n\n<\/a><\/figure><\/div>\n\n\n\n
<\/i> Download<\/h3>\n\n\n\n
- Stripe-Customer-Create-2021.xml<\/a><\/li><\/ul>\n\n\n\n
2021-06-07 (C) Questetra, Inc. (MIT License)
https:\/\/support.questetra.com\/addons\/stripe-customer-create-2021\/<\/a>
<\/i> The Addon-import feature is available with Professional<\/strong><\/span> edition.<\/p>\n\n\n<\/div>\n\n\n\n<\/i> Notes<\/h3>\n\n\n\n
- Create a “Customer object” on Stripe using Token.
- An environment for recurring charges will be built on Stripe.<\/li>
- Eg. place it after the “Payment card registration” step in the order handling workflow.<\/li><\/ul><\/li>
- A Tokenization mechanism (card registration form) is required.
- Refer to the sample below for how to implement the card registration form (tokenization).
- “Elements” (custom payment forms)
- https:\/\/stripe.com\/docs\/stripe-js<\/a><\/li>
- https:\/\/support.questetra.com\/tips\/form-decoration-examples\/#tokenize<\/a><\/li><\/ul><\/li>
- “Checkout” (forms hosted on Stripe)
- https:\/\/stripe.com\/docs\/payments\/checkout<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/li>
- Use the customer object ID (CustomerID) for flat-rate billing and usage billing.
- Can be obtained in this creation process. Example “cus_XXXXXYYYYYZZZZ”<\/li><\/ul><\/li><\/ul>\n\n\n\n
<\/i> Capture<\/h3>\n\n\n\n
![\"Creates](\"https:\/\/i0.wp.com\/support.questetra.com\/wp-content\/uploads\/2021\/06\/stripe-customer-create-2021-capture-en.png?resize=1200%2C675&ssl=1\")
<\/a><\/figure>\n\n\n\n![\"Creates](\"https:\/\/i0.wp.com\/support.questetra.com\/wp-content\/uploads\/2021\/06\/stripe-customer-create-2021-config-en.png?resize=991%2C1144&ssl=1\")
<\/a><\/figure>\n\n\n\n<\/i> Appendix<\/h3>\n\n\n\n
- PCI DSS Compliance (SAQ A) is to ensure that payment card data never touches any server.
- https:\/\/stripe.com\/docs\/security\/guide<\/a><\/li>
- This automated step allows you to build a system that does not retain sensitive info with no-code.<\/li><\/ul><\/li>
- Set Stripe SecretKey in “HTTP Authentication” > “Token Fixed Value”
- “sk_live_XXXXXyyyyyZZZZZxxxxxYYYY” (32 letters)<\/li><\/ul><\/li>
- For the contents of the error code (ResponseCode other than 200)
- https:\/\/stripe.com\/docs\/api\/errors<\/a><\/li><\/ul><\/li>
- When migrating from the old version (2020-06-03), add a new one instead of updating.
- The method of setting SecretKey has changed. (To be hidden)<\/li>
- https:\/\/support.questetra.com\/addons\/stripe-customer-object-create\/<\/a><\/li>
- Add a new Addon to the workflow app (Maage Add-on > Definition of Service task > Add)<\/li>
- Added “Token Fixed Value” at “HTTP Authz Settings”<\/li>
- In the modeler, place the new version of the add-on and remove the old version of the add-on.<\/li>
- Release workflow app.<\/li><\/ul><\/li><\/ul>\n\n\n\n
<\/i> Glossary<\/h3>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/support.questetra.com\/wp-content\/uploads\/2020\/06\/stripe-payment-payout-transfer.png?resize=1200%2C675&ssl=1\")
<\/figure>\n\n\n\n<\/i> See also<\/h3>\n\n\n\n
- When migrating from the old version (2020-06-03), add a new one instead of updating.
- https:\/\/stripe.com\/docs\/api\/errors<\/a><\/li><\/ul><\/li>
- https:\/\/stripe.com\/docs\/security\/guide<\/a><\/li>
- PCI DSS Compliance (SAQ A) is to ensure that payment card data never touches any server.
- Use the customer object ID (CustomerID) for flat-rate billing and usage billing.
- https:\/\/support.questetra.com\/tips\/form-decoration-examples\/#tokenize<\/a><\/li><\/ul><\/li>
- https:\/\/stripe.com\/docs\/stripe-js<\/a><\/li>
- “Elements” (custom payment forms)
- Refer to the sample below for how to implement the card registration form (tokenization).
- Create a “Customer object” on Stripe using Token.
- <\/i><\/span> B: Set Token *<\/span>#{EL}<\/sup><\/span><\/li>\n