Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.<\/p>\n
Include TrueMoney in the list of available payment methods.<\/p>\n
We provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos<\/a>.<\/p>\n<\/div><\/div>\nIf you are using the \/paymentMethods<\/a> to show available payment methods to the shopper, specify the following:<\/p>\n\n countryCode<\/a>: Any supported country\/region. For example, TH<\/strong>.<\/li>\n amount.currency<\/a>: Any supported currency. For example, THB<\/strong>.<\/li>\n amount.value<\/a>: The value of the payment, in minor units<\/a>.<\/li>\n channel<\/a>: Specify Web<\/strong><\/span>, iOS<\/strong><\/span>, or Android<\/strong><\/span>.<\/li>\n<\/ul>\nThe response contains paymentMethod.type<\/code>: truemoney<\/strong><\/span> for Web, or <\/strong> for iOS and Android.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: truemoney<\/strong><\/span><\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
If you are using the \/paymentMethods<\/a> to show available payment methods to the shopper, specify the following:<\/p>\n\n countryCode<\/a>: Any supported country\/region. For example, TH<\/strong>.<\/li>\n amount.currency<\/a>: Any supported currency. For example, THB<\/strong>.<\/li>\n amount.value<\/a>: The value of the payment, in minor units<\/a>.<\/li>\n channel<\/a>: Specify Web<\/strong><\/span>, iOS<\/strong><\/span>, or Android<\/strong><\/span>.<\/li>\n<\/ul>\nThe response contains paymentMethod.type<\/code>: truemoney<\/strong><\/span> for Web, or <\/strong> for iOS and Android.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: truemoney<\/strong><\/span><\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
The response contains paymentMethod.type<\/code>: truemoney<\/strong><\/span> for Web, or <\/strong> for iOS and Android.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: truemoney<\/strong><\/span><\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
paymentMethod.type<\/code>: truemoney<\/strong><\/span> for Web, or <\/strong> for iOS and Android.<\/p>\nMake a payment<\/h2>\nFrom your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: truemoney<\/strong><\/span><\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
From your server, make a \/payments<\/a> request, specifying:<\/p>\n\npaymentMethod.type<\/code>: truemoney<\/strong><\/span><\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
paymentMethod.type<\/code>: truemoney<\/strong><\/span><\/li>\n<\/ul>\n\n <\/code-sample>\n<\/div>\nIn the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
In the \/payments<\/a> response, check the action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
action<\/code> object for the information that you must use to redirect the shopper.<\/p>\n\n <\/code-sample>\n<\/div>\nHandle the redirect<\/h2>\n\n\nTo complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
To complete the payment, redirect the shopper to the action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
action.url<\/code> returned in the \/payments<\/a> response, taking into account the following recommendations:<\/p>\n\n\nWhen using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
When using the HTTP GET method:<\/strong>\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController<\/a> for iOS or Chrome Custom Tabs<\/a> for Android, instead of WebView objects. Also refer to the security best practices<\/a> for WebView.<\/p>\n<\/li>\n\nRedirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Redirection for mobile integrations:<\/strong>\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
After the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details<\/a> request, specifying:<\/p>\n\ndetails<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
details<\/code>: object that contains the URL-decoded redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
redirectResult<\/code> returned when the shopper was redirected back to your site.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n\nIn the response note the following:<\/p>\n\nresultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
In the response note the following:<\/p>\n
resultCode<\/code>: use this to present the result to your shopper.<\/li>\npspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
pspReference<\/code>: our unique identifier for the transaction.<\/li>\n<\/ul>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ol>\nPresent the payment result<\/h2>\nUse the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Use the resultCode<\/a> that you received in the \/payments\/details<\/a> response to present the payment result to your shopper.<\/p>\nThe resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
The resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
resultCode<\/code> values you can receive for TrueMoney are:<\/p>\n\n\n\nresultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAuthorised<\/strong><\/span><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.<\/td>\n<\/tr>\n\nCancelled<\/strong><\/span><\/td>\nThe shopper cancelled the payment while on TrueMoney's website.<\/td>\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n\nError<\/strong><\/span><\/td>\nThere was an error when the payment was being processed.<\/td>\nInform the shopper that there was an error processing their payment. The response contains a refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
refusalReason<\/code>, indicating the cause of the error.<\/td>\n<\/tr>\n\nPending<\/strong><\/span> or Received<\/strong><\/span><\/td>\nThe shopper has completed the payment but the final result is not yet known.<\/td>\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION<\/strong><\/span> webhook.<\/td>\n<\/tr>\n\nRefused<\/strong><\/span><\/td>\nThe payment was refused by the TrueMoney.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n\n\n\neventCode<\/th>\nsuccess field<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n\n\nAUTHORISATION<\/strong><\/span><\/td>\nfalse<\/strong><\/span><\/td>\nThe transaction failed.<\/td>\nCancel the order and inform the shopper that the payment failed.<\/td>\n<\/tr>\n\nAUTHORISATION<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper successfully completed the payment.<\/td>\nInform the shopper that the payment has been successful and proceed with the order.<\/td>\n<\/tr>\n\nOFFER_CLOSED<\/strong><\/span><\/td>\ntrue<\/strong><\/span><\/td>\nThe shopper did not complete the payment.<\/td>\nCancel the order and inform the shopper that the payment timed out.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nRecurring payments<\/h2>\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token<\/a>.<\/li>\nUse the token to make future payments for the shopper<\/a>.<\/li>\n<\/ol>\nCreate a token<\/h3>\nTo create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
<\/a> If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:<\/p>\n
To create a token, include in your \/payments<\/a> request:<\/p>\n\nstorePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
storePaymentMethod<\/code>: true<\/strong><\/span><\/li>\n shopperReference<\/a>: Your unique identifier for the shopper.<\/li>\n<\/ul>\nThis triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
This triggers the recurring flow<\/a>, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.<\/p>\n\nFor the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
For the recurring flow to be completed, always make the \/payments\/details<\/a> request, otherwise the payment method will not be stored.<\/p>\n<\/div>\nWhen the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
When the payment has been settled, you receive a recurring.token.created<\/a> webhook<\/a> containing:<\/p>\n\ntype<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
type<\/code>: recurring.token.created<\/strong><\/span><\/li>\nshopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
shopperReference<\/code>: your unique identifier for the shopper.<\/li>\neventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
eventId<\/code>: the pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
pspReference<\/code> of the initial payment.<\/li>\nstoredPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
storedPaymentMethodId<\/code>: the token that you need to make recurring payments for this shopper.<\/li>\n<\/ul>\n\nMake sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Make sure that your server is able to receive the Recurring tokens life cycle events<\/a> webhook. You can set up this webhook in your Customer Area<\/a>.<\/p>\n<\/div>\nMake a payment with a token<\/h3>\nTo make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
To make a payment with the token, include in your \/payments<\/a> request:<\/p>\n\n\npaymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
paymentMethod.storedPaymentMethodId<\/code>: The storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
storedPaymentMethodId<\/code> from the recurring.token.created<\/a> webhook or from additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
additionalData.tokenization.storedPaymentMethodId<\/code> if you are retrieving the token synchronously.<\/p>\n\nYou can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
You can also get this value using the \/listRecurringDetails<\/a> endpoint.<\/p>\n<\/div>\n<\/li>\n\nshopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
shopperReference<\/code>: The unique shopper identifier that you specified when creating the token.<\/p>\n<\/li>\n\nshopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
shopperInteraction<\/code>:\u00a0ContAuth<\/strong><\/span><\/p>\n<\/li>\n\nrecurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
recurringProcessingModel<\/code>: Use Subscription<\/strong><\/span> for a series of transactions following a fixed time interval or UnscheduledCardOnFile<\/strong><\/span> for contracts with non-fixed time interval.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n<\/ul>\nTest and go live<\/h2>\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
To test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account<\/a>.<\/p>\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
If you are encountering issues with testing TrueMoney payments, contact our Support Team<\/a>.<\/p>\nCheck the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Check the status of TrueMoney test payments in your\u00a0Customer Area<\/a>\u00a0>\u00a0Payments<\/strong>\u00a0>\u00a0Payment list<\/strong>.<\/p>\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
Before you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area<\/a>.<\/p>\nSee also<\/h2>\n\n\n API only integration\n <\/a><\/li>\n Webhooks\n <\/a><\/li>\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","articleFields":{"description":"Add TrueMoney to an existing API-only integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"https:\/\/your-company.example.com\/checkout?shopperOrder=12xy..","component_name":"truemoney","integration":"API-only","platform":"Web"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/api-only","title":"TrueMoney for API-only","content":"Accept TrueMoney payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an API-only integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your test Customer Area.\n\n\n\nBuild your payment form for TrueMoney\nInclude TrueMoney in the list of available payment methods.\n\nWe provide logos for TrueMoney which you can use on your payment form. For more information, refer to Downloading logos.\n\nIf you are using the \/paymentMethods to show available payment methods to the shopper, specify the following:\n\n countryCode: Any supported country\/region. For example, TH.\n amount.currency: Any supported currency. For example, THB.\n amount.value: The value of the payment, in minor units.\n channel: Specify Web, iOS, or Android.\n\nThe response contains paymentMethod.type: truemoney for Web, or for iOS and Android.\nMake a payment\nFrom your server, make a \/payments request, specifying:\n\npaymentMethod.type: truemoney\n\n\n \n\nIn the \/payments response, check the action object for the information that you must use to redirect the shopper.\n\n \n\nHandle the redirect\n\n\nTo complete the payment, redirect the shopper to the action.url returned in the \/payments response, taking into account the following recommendations:\n\n\nWhen using the HTTP GET method:\nFor security reasons, when showing the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.\n\n\nRedirection for mobile integrations:\nFor mobile integrations, we strongly recommended that you redirect the shopper to the default browser of their device. Redirecting to the default browser ensures the best compatibility, handling of multi-factor authentication, app-to-app redirection, and error handling.\n\n\n\n\nAfter the shopper is redirected back to your website, check the payment result by making a POST \/payments\/details request, specifying:\n\ndetails: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.\n\n\n\n\n\n\nIn the response note the following:\n\nresultCode: use this to present the result to your shopper.\npspReference: our unique identifier for the transaction.\n\n\n\n\n\n\nPresent the payment result\nUse the resultCode that you received in the \/payments\/details response to present the payment result to your shopper.\nThe resultCode values you can receive for TrueMoney are:\n\n\n\nresultCode\nDescription\nAction to take\n\n\n\n\nAuthorised\nThe payment was successful.\nInform the shopper that the payment has been successful.\n\n\nCancelled\nThe shopper cancelled the payment while on TrueMoney's website.\nAsk the shopper whether they want to continue with the order, or ask them to select a different payment method.\n\n\nError\nThere was an error when the payment was being processed.\nInform the shopper that there was an error processing their payment. The response contains a refusalReason, indicating the cause of the error.\n\n\nPending or Received\nThe shopper has completed the payment but the final result is not yet known.\nInform the shopper that you have received their order, and are waiting for the payment to be completed. To know the final result of the payment, wait for the AUTHORISATION webhook.\n\n\nRefused\nThe payment was refused by the TrueMoney.\nAsk the shopper to try the payment again using a different payment method.\n\n\n\n If the shopper closed the browser and failed to return to your website, wait for webhooks to know the outcome of the payment. The webhooks you can receive for TrueMoney are:\n\n\n\neventCode\nsuccess field\nDescription\nAction to take\n\n\n\n\nAUTHORISATION\nfalse\nThe transaction failed.\nCancel the order and inform the shopper that the payment failed.\n\n\nAUTHORISATION\ntrue\nThe shopper successfully completed the payment.\nInform the shopper that the payment has been successful and proceed with the order.\n\n\nOFFER_CLOSED\ntrue\nThe shopper did not complete the payment.\nCancel the order and inform the shopper that the payment timed out.\n\n\n\nRecurring payments\nTrueMoney supports recurring transactions. To make recurring transactions, you need to:\n\nCreate a shopper token.\nUse the token to make future payments for the shopper.\n\nCreate a token\nTo create a token, include in your \/payments request:\n\nstorePaymentMethod: true\n shopperReference: Your unique identifier for the shopper.\n\nThis triggers the recurring flow, where the shopper logs in to their TrueMoney account, and then confirms the recurring transaction.\n\nFor the recurring flow to be completed, always make the \/payments\/details request, otherwise the payment method will not be stored.\n\nWhen the payment has been settled, you receive a recurring.token.created webhook containing:\n\ntype: recurring.token.created\nshopperReference: your unique identifier for the shopper.\neventId: the pspReference of the initial payment.\nstoredPaymentMethodId: the token that you need to make recurring payments for this shopper.\n\n\nMake sure that your server is able to receive the Recurring tokens life cycle events webhook. You can set up this webhook in your Customer Area.\n\nMake a payment with a token\nTo make a payment with the token, include in your \/payments request:\n\n\npaymentMethod.storedPaymentMethodId: The storedPaymentMethodId from the recurring.token.created webhook or from additionalData.tokenization.storedPaymentMethodId if you are retrieving the token synchronously.\n\nYou can also get this value using the \/listRecurringDetails endpoint.\n\n\n\nshopperReference: The unique shopper identifier that you specified when creating the token.\n\n\nshopperInteraction:\u00a0ContAuth\n\n\nrecurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.\n\n\n\n\n\nTest and go live\nTo test successful TrueMoney live payments, you need to use a real mobile number registered with a TrueMoney account.\nIf you are encountering issues with testing TrueMoney payments, contact our Support Team.\nCheck the status of TrueMoney test payments in your\u00a0Customer Area\u00a0>\u00a0Payments\u00a0>\u00a0Payment list.\nBefore you can accept live TrueMoney payments, you need to submit a request for TrueMoney in your live Customer Area.\nSee also\n\n\n API only integration\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney for API-only"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"\/payment-methods\/truemoney\/api-only"},"levels":4,"category":"Payment method","category_color":"green","tags":["TrueMoney","API-only"]},"articleFiles":{"payments.js":"payments.js<\/p>"}}
payments.js<\/p>"}}