\n API Explorer\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/android-drop-in\/earlier-versions","articleFields":{"description":"Add TrueMoney to an existing Drop-in integration.","parameters":{"payment_method":"TrueMoney","country_code":"TH","currency":"THB","payment_method_type":"truemoney","return_url":"adyencheckout:\/\/your.package.name","integration":"Drop-in","platform":"Android"}},"algolia":{"url":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/android-drop-in\/earlier-versions","title":"TrueMoney Drop-in v4.x.x integration","content":"Our Android Drop-in renders TrueMoney in your payment form, and redirects the shopper to the TrueMoney's website where they can complete the payment.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nMake sure that you have built an Advanced flow Android Drop-in integration. \n\n\nSetup steps\nBefore you begin, add TrueMoney in your Customer Area.\n\n\n\nShow TrueMoney in your payment form\nDrop-in uses the countryCode and the amount.currency from your \/paymentMethods request to show the available payment methods to your shopper.\nTo show TrueMoney in your payment form, specify in your \/paymentMethods request:\n\n countryCode: TH.\n amount.currency: THB.\n amount.value: The value of the payment.\n\nMake a payment\nWhen the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod.\n\nPass the paymentComponentData.paymentMethod to your server.\nFrom your server, make a \/payments request, specifying:\n\n paymentMethod: The paymentComponentData.paymentMethod from your client app.\n returnUrl: URL to where the shopper should be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters. Get this URL from the Component in the RedirectComponent.getReturnUrl(context).\n\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\nIf your integration is set up correctly, the action object is passed from your server to the client.\nCheck the payment result\nDrop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the actionComponentData object.\n \nFrom your server, make a POST \/payments\/details request providing:\n\ndetails: The actionComponentData.details object from Drop-in.\n\n\n \n\nYou receive a response containing:\n\nresultCode: Use this to present the payment result to your shopper.\npspReference: Our unique identifier for the transaction.\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 Android Drop-in integration guide\n \n Webhooks\n \n API Explorer\n \n","type":"page","locale":"en","boost":16,"hierarchy":{"lvl0":"Home","lvl1":"Payment methods","lvl2":"TrueMoney","lvl3":"TrueMoney Drop-in integration","lvl4":"TrueMoney Drop-in v4.x.x integration"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/payment-methods","lvl2":"https:\/\/docs.adyen.com\/payment-methods\/truemoney","lvl3":"https:\/\/docs.adyen.com\/payment-methods\/truemoney\/android-drop-in","lvl4":"\/payment-methods\/truemoney\/android-drop-in\/earlier-versions"},"levels":5,"category":"Payment method","category_color":"green","tags":["TrueMoney","Drop-in","v4.x.x","integration"]},"articleFiles":{"android-payments.js":"android-payments.js<\/p>"}}