<i id='qgvtn'><tr id='qgvtn'><dt id='qgvtn'><q id='qgvtn'><span id='qgvtn'><b id='qgvtn'><form id='qgvtn'><ins id='qgvtn'></ins><ul id='qgvtn'></ul><sub id='qgvtn'></sub></form><legend id='qgvtn'></legend><bdo id='qgvtn'><pre id='qgvtn'><center id='qgvtn'></center></pre></bdo></b><th id='qgvtn'></th></span></q></dt></tr></i><div id='qgvtn'><tfoot id='qgvtn'></tfoot><dl id='qgvtn'><fieldset id='qgvtn'></fieldset></dl></div>
  • <legend id='qgvtn'><style id='qgvtn'><dir id='qgvtn'><q id='qgvtn'></q></dir></style></legend>
      <bdo id='qgvtn'></bdo><ul id='qgvtn'></ul>

      1. <tfoot id='qgvtn'></tfoot>
      2. <small id='qgvtn'></small><noframes id='qgvtn'>

        是否有多种格式的 In App Billing 交易?

        时间:2024-04-14

      3. <small id='ZjsX0'></small><noframes id='ZjsX0'>

        <legend id='ZjsX0'><style id='ZjsX0'><dir id='ZjsX0'><q id='ZjsX0'></q></dir></style></legend>

        • <i id='ZjsX0'><tr id='ZjsX0'><dt id='ZjsX0'><q id='ZjsX0'><span id='ZjsX0'><b id='ZjsX0'><form id='ZjsX0'><ins id='ZjsX0'></ins><ul id='ZjsX0'></ul><sub id='ZjsX0'></sub></form><legend id='ZjsX0'></legend><bdo id='ZjsX0'><pre id='ZjsX0'><center id='ZjsX0'></center></pre></bdo></b><th id='ZjsX0'></th></span></q></dt></tr></i><div id='ZjsX0'><tfoot id='ZjsX0'></tfoot><dl id='ZjsX0'><fieldset id='ZjsX0'></fieldset></dl></div>
            <bdo id='ZjsX0'></bdo><ul id='ZjsX0'></ul>

            • <tfoot id='ZjsX0'></tfoot>
                  <tbody id='ZjsX0'></tbody>

                  本文介绍了是否有多种格式的 In App Billing 交易?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                  问题描述

                  我们在验证某些付款交易(Google In App Billing V3)时遇到问题.看起来繁琐交易的数据与我们在验证没有问题的交易中看到的格式不同.

                  We're having problems verifying some of payment transactions (Google In App Billing V3). It looks like data of cumbersome transactions follows a different format than what we can see in transactions we have no problems verifying.

                  • OrderId:用点分隔的两个数字:92299713162054702728.1224255970239541
                  • 签名:始终在末尾包含 base64 填充,长度为 345 个字符
                  • OrderId: Two numbers separated with a dot: 92299713162054702728.1224255970239541
                  • Signature: Always includes base64 padding at the end, 345 characters long
                  • OrderId:一个号码:5643493869375537013
                  • 签名:缺少 base64 填充,长度为 343 个字符
                  • OrderId: One number: 5643493869375537013
                  • Signature: Is missing base64 padding, 343 characters long

                  (这些不是实际的 ID)

                  (those are not actual ids)

                  在缺少填充时手动添加填充无助于验证签名.

                  Adding padding manually when it's missing does not help to verify signatures.

                  为什么我们会收到不同格式的数据?为什么我们无法验证它们,即使我们在验证普通"交易时没有问题?为了解决这个问题,我们应该做什么/调查?

                  Why are we receiving data in different format? Why are we unable to verify them, even though we have no problems verifying "ordinary" transactions? What should we do / investigate in order to solve this issue?

                  推荐答案

                  查看此链接:

                  http://developer.android.com/google/play/billing/billing_admin.html#orderId

                  For transactions dated 5 December 2012 or later, Google Wallet assigns a Merchant Order Number (rather than a Google Order Number) and reports the Merchant Order Number as the value of orderID. Here's an example:
                  
                  "orderId" : "12999556515565155651.5565135565155651"
                  For transactions dated previous to 5 December 2012, Google checkout assigned a Google Order Number and reported that number as the value of orderID. Here's an example of an orderID holding a Google Order Number:
                  
                  "orderId" : "556515565155651"
                  

                  所以我认为您可以通过将日期明智的交易存储在您的数据库中并检查日期是否给定日期是 12 月 5 日或更晚然后检查第一个其他第二个来解决它.

                  So I think you can solved it by storing date wise transaction in your database and check the date whether given date is 5 Dec or later then check 1st one else 2nd one.

                  您还可以检查开发人员有效负载以检查我们的交易是否安全完成.Google Play 商店将为您提供与购买应用内产品时相同的有效负载.

                  you can also check the developer payload to check whether our transaction is securely done or not. Google play store will give you the same payload that you gave while purchasing the in app product.

                  有关更多信息,请查看此链接以获取开发人员有效负载 链接

                  For more information check this link for the developer payload link

                  希望它能解决你的问题.

                  Hope it will solve your problem.

                  这篇关于是否有多种格式的 In App Billing 交易?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                  上一篇:Swift 中的 base64EncodedStringWithOptions 因编译错误而失败 下一篇:如何将 NSData 编码为 base64?(iPhone/iPad)

                  相关文章

                    <i id='ot4o4'><tr id='ot4o4'><dt id='ot4o4'><q id='ot4o4'><span id='ot4o4'><b id='ot4o4'><form id='ot4o4'><ins id='ot4o4'></ins><ul id='ot4o4'></ul><sub id='ot4o4'></sub></form><legend id='ot4o4'></legend><bdo id='ot4o4'><pre id='ot4o4'><center id='ot4o4'></center></pre></bdo></b><th id='ot4o4'></th></span></q></dt></tr></i><div id='ot4o4'><tfoot id='ot4o4'></tfoot><dl id='ot4o4'><fieldset id='ot4o4'></fieldset></dl></div>

                      <small id='ot4o4'></small><noframes id='ot4o4'>

                        <bdo id='ot4o4'></bdo><ul id='ot4o4'></ul>

                      <tfoot id='ot4o4'></tfoot>

                    1. <legend id='ot4o4'><style id='ot4o4'><dir id='ot4o4'><q id='ot4o4'></q></dir></style></legend>