> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/error-codes.md).

# Error Codes

<table><thead><tr><th width="133">Error Code</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>General unknown error<br><br>a. Payment channel error not existing/mapped on Coda system<br>b. The Coda system did not receive a successful/valid response from the payment channel</td></tr><tr><td>101</td><td>This error indicates that there's an internal error from Coda's side.</td></tr><tr><td>102</td><td>This error indicates that there's an internal connection error from Coda's side.</td></tr><tr><td>103</td><td>A parameter in the request message sent to Coda is incorrect. Please check your parameters or send your transaction logs to Coda's technical support team for investigation.</td></tr><tr><td>104</td><td>This error indicates that there's an internal error from Coda's side.</td></tr><tr><td>151</td><td>This error occurs when there is an unknown error.</td></tr><tr><td>201</td><td>This error occurs when there is an unknown error from the payment channel's side.</td></tr><tr><td>202</td><td>This error occurs during an integration when one of the parameters indicated in the Merchant's API request to Coda is incorrect. Please contact our technical team for support.</td></tr><tr><td>203</td><td>Occurs when the charge amount submitted by the merchant includes a decimal. (i.e. Rp. 5000.99).</td></tr><tr><td>204</td><td>Your API key or URLs have not yet been registered in Coda’s system.</td></tr><tr><td>205</td><td>This error occurs when a merchant's sandbox system points to Coda's production system, but the status in Coda's production system is still "Testing". In this case, the merchant should change their airtime URL to the sandbox URL and continue testing. This error also occurs when a merchant's production system points to Coda's production system, but the merchant account is not active in Coda's production system. In this case, the merchant should contact Coda to activate their account.</td></tr><tr><td>206</td><td>During testing, this error occurs when the merchant calls Coda's Init() method from their sandbox environment, but then makes an Airtime_Checkout() Javascript call to Coda's production environment using the transaction ID that was generated in the sandbox service environment. When in production, this error occurs when the merchant calls Coda's Init() method, but then does not make an Airtime_Checkout() Javascript call within 15 minutes and the transaction ID expires.</td></tr><tr><td>207</td><td>This occurs when there is an error in the transaction update.</td></tr><tr><td>208</td><td>This occurs when the transaction status is invalid.</td></tr><tr><td>209</td><td>This occurs when the status is pending in user action/server response, There is nothing wrong with this transaction.</td></tr><tr><td>210</td><td>This occurs when the user cancels the payment on our page, There is nothing wrong with this transaction.</td></tr><tr><td>211</td><td>This occurs when a user’s transaction expires before they respond with the correct OTP.</td></tr><tr><td>212</td><td>The transaction completion URL that you provided to Coda is not valid (i.e. there is a problem with the format) or has not yet been registered.</td></tr><tr><td>213</td><td>This error occurs when a customer initiates a transaction but does not complete it by responding with the correct OTP during the session time (for DCB) or paying at a store (bank or convenience store). Hence, it's counted as an expired transaction.</td></tr><tr><td>214</td><td>The format or value of your request to Coda is invalid.</td></tr><tr><td>215</td><td>This error indicates that the SMS has already been sent to the customer.</td></tr><tr><td>216</td><td>This error occurs when a customer initiates a transaction, and enters their mobile number, but does not reply with an OTP. For ATM and OTC transactions, this error can be ignored: it only indicates that the transaction has been initiated but not yet completed (there is no problem with the transaction).</td></tr><tr><td>217</td><td>This error occurs when a user initiates a transaction using an MSISDN with which a transaction has been initiated but not yet completed within the previous 5 minutes.</td></tr><tr><td>218</td><td>This error occurs when a user initiates a transaction using the same IP address with which a transaction has been initiated but not yet completed within the previous 5 minutes.</td></tr><tr><td>219</td><td>This error occurs when there's a database error.</td></tr><tr><td>220</td><td>The country code and/or currency code that you filed is not valid.</td></tr><tr><td>221</td><td>This error indicates that the transaction has already been canceled.</td></tr><tr><td>222</td><td>This error occurs when the customer attempts to enter an incorrect OTP too many times.</td></tr><tr><td>223</td><td>This error occurs when the customer enters an invalid OTP</td></tr><tr><td>224</td><td>This error occurs when the user has manually blocked their account in the customer portal.</td></tr><tr><td>225</td><td>This error occurs during an integration when a payment channel is being tested but has not yet been activated in our system. Please contact our technical team for support.</td></tr><tr><td>226</td><td>This error occurs when a user has entered an invalid mobile number. Please contact our technical team for support.</td></tr><tr><td>227</td><td>This error occurs when the customer attempts to complete a purchase at a price point that Coda has not registered with a particular telco.<br>Please contact Coda's technical support team for a list of available price points.</td></tr><tr><td>228</td><td>This error occurs when the transaction session times out but the payment channel receives a successful transaction. Contact our support team for more information.</td></tr><tr><td>229</td><td>This error occurs when the transaction session times out before a response from the telco is received to the charge request.</td></tr><tr><td>230</td><td>Transaction expired but failed from Operator side.</td></tr><tr><td>231</td><td>Transaction already marked as completed, cannot be processed again.</td></tr><tr><td>232</td><td>Occurs when a customer initiates a new transaction that in turn cancels the previous one (this one).</td></tr><tr><td>233</td><td>This error occurs during integration when a merchant implements Coda's payment channel selection page (Paytype = 0), but has not yet configured it Coda Portal<br><br>Please ensure these steps has been completed<br>1. Payment Channel e-annex has been approved (Coda Portal > Payment Method)<br>2. Payment Channel Selection Page configuration has been completed (Coda Portal > Codapay > Production Configuration > Edit > Coda Payment Page Configuration </td></tr><tr><td>234</td><td>Received unsupported operation from the payment channel.</td></tr><tr><td>235</td><td>This error occurs when you are using our backend API and we haven't enabled it on our end. Please contact our support team.</td></tr><tr><td>236</td><td>The transaction does not belong to the merchant.</td></tr><tr><td>237</td><td>This error occurs when the user_id parameter is missing in the init request. For more details please refer to <a href="https://codapayments.readme.io/docs/profile-fields">Profile Fields</a></td></tr><tr><td>238</td><td>This error occurs when our USD conversion system is down.</td></tr><tr><td>239</td><td>This error occurs when there is an error in the checksum validation.</td></tr><tr><td>240</td><td>Occurs when the phone number of a carrier billing that is entered on the payment page is a different type of carrier billing selected by the customer</td></tr><tr><td>241</td><td>This error occurs when the transaction is older than 3 months and cannot proceed with the payment.</td></tr><tr><td>242</td><td>This error occurs when a payment channel doesn't support desktop devices. Please advise the user to make the payment using a mobile device.</td></tr><tr><td>243</td><td>This error occurs when the token is expired.</td></tr><tr><td>244</td><td>This error occurs when the application is updating.</td></tr><tr><td>245</td><td>Occurs when the KYC is not completed.</td></tr><tr><td>246</td><td>Occurs when the account is not found on the payment channel's side.</td></tr><tr><td>247</td><td>Occurs when the customer is not eligible to make the transaction to the payment channel.</td></tr><tr><td>248</td><td>Invalid CPF, please verify your date of birth and CPF number.</td></tr><tr><td>249</td><td>Invalid CNPJ, please verify your CNPJ number.</td></tr><tr><td>250</td><td>Different name from the federal revenue register of natural persons.</td></tr><tr><td>251</td><td>The return URL provided is invalid.</td></tr><tr><td>252</td><td>Return URL exceeds allowed length or limit.</td></tr><tr><td>253</td><td>General processing error, unspecified failure.</td></tr><tr><td>254</td><td>The transaction was closed since the user has clicked back on their browser, and will not be able to resume.</td></tr><tr><td>301</td><td>Occurs when the blacklist does not exist.</td></tr><tr><td>309</td><td>One or more parameters included in this transaction have been blacklisted.</td></tr><tr><td>310</td><td>One or more parameters included in this transaction have been blacklisted.</td></tr><tr><td>311</td><td>One or more parameters included in this transaction have been blacklisted.</td></tr><tr><td>312</td><td>This error occurs when a transaction violates one or more risk rules. In this case, merchants should advise customers to contact Coda for more information.<br><br>This also means that the payment channel is down at the moment. Please check with our Support team.</td></tr><tr><td>313</td><td>Occurs when the device ID has been blacklisted.</td></tr><tr><td>314</td><td>One or more parameters included in this transaction have been blacklisted.</td></tr><tr><td>315</td><td>One or more parameters included in this transaction have been blacklisted.</td></tr><tr><td>316</td><td>Customer user IDs have been blacklisted. Please advise the customer to send an email to <a href="mailto:fraud@codashop.com">fraud@codashop.com</a> requesting removal from the blacklist.</td></tr><tr><td>319</td><td>This transaction was automatically declined by the Coda risk management system. Please contact our Support team for further information.</td></tr><tr><td>350</td><td>The Subscription Plan ID field was empty in the request message. This field is mandatory for subscription requests.</td></tr><tr><td>351</td><td>The Subscription Plan does not exist.</td></tr><tr><td>352</td><td>The phone number is already subscribed to this plan. Only one subscription per number is allowed.</td></tr><tr><td>353</td><td>The phone number is already subscribed to another plan. Only one subscription per merchant is allowed.</td></tr><tr><td>354</td><td>Invalid subscription plan keyword.</td></tr><tr><td>355</td><td>There is no subscription linked to the phone number in the request.</td></tr><tr><td>356</td><td>The mobile number already unsubscribed from this plan</td></tr><tr><td>357</td><td>The mobile number already unsubscribed from this plan</td></tr><tr><td>358</td><td>Invalid MO for the subscription plan.</td></tr><tr><td>359</td><td>The subscription you tried to access is not linked to your merchant account.</td></tr><tr><td>360</td><td>The price in your request message does not match the price defined on the subscription plan.</td></tr><tr><td>361</td><td>This payment channel currently does not support subscription payments.</td></tr><tr><td>362</td><td>The subscription payments return an invalid status.</td></tr><tr><td>363</td><td>The subscription payments could not verify the VPA.</td></tr><tr><td>364</td><td>The subscription session token has expired.</td></tr><tr><td>365</td><td>The payment channel does not support subscriptions.</td></tr><tr><td>367</td><td>Invalid subscription token.</td></tr><tr><td>368</td><td>The attempt to retry the renewal subscription has been exceeded.</td></tr><tr><td>401</td><td>This message will be displayed when a user attempts to complete a transaction using an MSISDN from a mobile operator with whom Coda is not connected.</td></tr><tr><td>402</td><td>This message will be displayed when a user attempts to complete a transaction using an MSISDN from a mobile operator with whom Coda is not connected.</td></tr><tr><td>403</td><td>Coda’s attempt to file a charge with a mobile operator failed for a technical reason. For True it's a general error that can mean the Voucher was USED, the Voucher was suspended, the Voucher was not found, the Voucher LOCKED, Duplicated Voucher was used.</td></tr><tr><td>404</td><td>Coda’s attempt to connect to the mobile operator failed.</td></tr><tr><td>405</td><td>The mobile operator with whom Coda filed a charge request could not validate the MSISDN that was submitted as part of the transaction. This likely occurs when the customer enters a MSISDN with a correct prefix but incorrect length.</td></tr><tr><td>406</td><td>Occurs when the payment channel returns invalid integration information.</td></tr><tr><td>407</td><td>Occurs when the payment channel with whom Coda filed the transaction has a technical error.</td></tr><tr><td>408</td><td>This error occurs when a user has entered an invalid parameter. Please contact our technical team for support.</td></tr><tr><td>409</td><td>This error occurs when the payment channel returns an error from Coda's side.</td></tr><tr><td>410</td><td>The mobile operator with whom Coda filed a charge request could not validate a parameter included in the transaction. For Maxis transactions, this means the MSISDN is from a different telco.</td></tr><tr><td>411</td><td>This error occurs when a merchant's name has not yet been registered on the Payment Channel system. Please contact our technical team for support.</td></tr><tr><td>412</td><td>This error occurs when Coda files a transaction with a mobile operator, but is informed that the mobile operator has an internal error.</td></tr><tr><td>413</td><td>Transaction not found or does not exist</td></tr><tr><td>414</td><td>The customer who initiated the transaction did not have sufficient balance on the MSISDN that they entered at the time of the transaction.</td></tr><tr><td>415</td><td>The value of the transaction attempted by the customer exceeded the value of a limit associated with their account. Alternatively, the transaction amount is not within the limits allowed for the payment channel, for example, ATM Transfer and Alfamart transactions in Indonesia have a minimum amount of Rp. 50.000.</td></tr><tr><td>416</td><td>The customer who initiated the transaction would not have had the required Rp. 1500 minimum balance remaining after the purchase was completed. No charge was made.</td></tr><tr><td>417</td><td>The MSISDN entered by the customer has churned or is expired.</td></tr><tr><td>418</td><td>The customer entered a postpaid MSISDN from a mobile operator that does not authorize postpaid transactions.</td></tr><tr><td>419</td><td>The mobile operator with whom Coda filed a charge request could pass the second validation of a parameter included in the transaction.</td></tr><tr><td>420</td><td>The number could not be charged as it is blocked by the operator.</td></tr><tr><td>421</td><td>This error occurs when the transaction does not pass the authorization to charge from the payment channel.</td></tr><tr><td>422</td><td>This error occurs when there is a duplicated authorization for the transaction under the payment channel.</td></tr><tr><td>423</td><td>This error occurs when the payment channel returns a service overload error from their system.</td></tr><tr><td>424</td><td>This error occurs when the payment channel fails to return the complete transaction notification to Coda.</td></tr><tr><td>425</td><td>This error occurs when the customer enters a prepaid mobile number, but their mobile operator does not authorize prepaid customers to use the service.</td></tr><tr><td>426</td><td>The payment channel is unable to process this transaction due to a capacity constraint.</td></tr><tr><td>427</td><td>This error occurs when the new subscriber is not allowed.</td></tr><tr><td>428</td><td>The number could not be charged as it is expired, in the grace period, or otherwise blocked by the operator.</td></tr><tr><td>429</td><td>This error occurs when a customer initiates a transaction at an amount that is not supported by their telco.</td></tr><tr><td>430</td><td>This error occurs when there is a duplicate charge request.</td></tr><tr><td>431</td><td>Occurs when the customer initiates an ATM/Alfamart transaction and we are waiting for them to complete it at the ATM. This error can be ignored: it only indicates that the transaction has been initiated but not yet completed (there is no problem with the transaction).</td></tr><tr><td>432</td><td>This error occurs when the transaction does not pass the pre-risk rule check from the payment channel.</td></tr><tr><td>433</td><td>The customer sent Coda their first confirmation MO (i.e. PAY X) but not the second (i.e. GO).</td></tr><tr><td>434</td><td>The customer did not respond to the confirmation of MO (i.e. PAY X).</td></tr><tr><td>435</td><td>This error occurs when the payment charge is still in progress.</td></tr><tr><td>436</td><td>This error happens when the amount the customer tries to pay does not match the amount on the transaction.</td></tr><tr><td>437</td><td>This error indicates that the customer responded with an invalid MO.</td></tr><tr><td>438</td><td>This error means that the transactions have expired. There is nothing wrong with this transaction.</td></tr><tr><td>439</td><td>This error means that the customer pays less amount for the transaction.</td></tr><tr><td>440</td><td>Occurs when there is a technical error with the telco billing system.</td></tr><tr><td>441</td><td>Occurs when the telco authorization is not supported by the payment channel.</td></tr><tr><td>442</td><td>Occurs when the customer's MO MSISDN is not matched with the transaction MSISDN.</td></tr><tr><td>443</td><td>The customer's MSISDN has exceeded their prepaid or postpaid service limit. This error is returned for the DCB type of payment channel.</td></tr><tr><td>444</td><td>The customer entered an account/phone number that the payment channel doesn't recognize</td></tr><tr><td>445</td><td>Occurs when the chosen payment method by the customer is not allowed by the payment channel.</td></tr><tr><td>446</td><td>Occurs when the MSISDN entered by the customer is not allowed.</td></tr><tr><td>447</td><td>Temporary issue, please retry the request later.</td></tr><tr><td>451</td><td>The selected payment channel is not registered with the payment service provider.</td></tr><tr><td>452</td><td>Reach maximum attempt to create the transaction with the selected payment channel.</td></tr><tr><td>453</td><td>Occurs when the words do not match.</td></tr><tr><td>454</td><td>Failed to notify the payment channel.</td></tr><tr><td>455</td><td>Occurs when re-entering the transaction.</td></tr><tr><td>456</td><td>The payment code has expired.</td></tr><tr><td>457</td><td>The transaction with the selected payment channel has been canceled by the user.</td></tr><tr><td>458</td><td>The transaction with the following payment code has not been paid by the customer.</td></tr><tr><td>459</td><td>The transaction is rejected by the fraud system of the payment channel.</td></tr><tr><td>460</td><td>The transaction has a duplicated PNR number.</td></tr><tr><td>461</td><td>There's an error in parsing the XML.</td></tr><tr><td>462</td><td>Occurs when the customer stops at the secure page.</td></tr><tr><td>463</td><td>The transaction is declined by the payment channel.</td></tr><tr><td>464</td><td>Occurs when the quick code that is required by the payment channel is invalid.</td></tr><tr><td>465</td><td>This error occurs when the amount the customer attempts to pay differs from the transaction amount.</td></tr><tr><td>466</td><td>Occurs when the currency code needed by the payment channel is invalid.</td></tr><tr><td>467</td><td>Occurs when the customer enters an invalid payee ID that is required by the payment channel.</td></tr><tr><td>468</td><td>Occurs when the customer enters an invalid customer ID that is required by the payment channel.</td></tr><tr><td>469</td><td>Occurs when the quick code that is required by the payment channel is missing.</td></tr><tr><td>470</td><td>Occurs when the payment channel returns an invalid bank error.</td></tr><tr><td>471</td><td>Occurs when the payment channel returns credit account is not supported error.</td></tr><tr><td>472</td><td>Occurs when the transaction is not allowed by the payment channel.</td></tr><tr><td>473</td><td>Occurs when the transaction frequency has exceeded the limit.</td></tr><tr><td>474</td><td>Occurs when the payment channel returns a bank error.</td></tr><tr><td>475</td><td>Occurs when the transaction is already time out from the payment channel's side.</td></tr><tr><td>476</td><td>Occurs when the payment channel returns an invalid IP error.</td></tr><tr><td>477</td><td>Occurs when the payment channel returns an invalid operation hours error.</td></tr><tr><td>478</td><td>Occurs when the payment is still in progress.</td></tr><tr><td>479</td><td>The payment channel returns an invalid payment code error.</td></tr><tr><td>480</td><td>Occurs when the payment code is invalid.</td></tr><tr><td>481</td><td>Occurs when the customer initiates an ATM/Alfamart transaction and we are waiting for them to complete it at the ATM. This error can be ignored: it only indicates that the transaction has been initiated but not yet completed (there is no problem with the transaction).</td></tr><tr><td>483</td><td>Occurs when the customer enters a mismatched code required by the payment channel.</td></tr><tr><td>492</td><td>Request failed due to too many requests.</td></tr><tr><td>493</td><td>User not eligible for Direct Carrier Billing.</td></tr><tr><td>494</td><td>Whitelist verification failed, user/device not allowed.</td></tr><tr><td>501</td><td>Transaction declined because the amount exceeded the merchant limit.</td></tr><tr><td>502</td><td>Transaction declined because the amount exceeded the user’s transaction limit.</td></tr><tr><td>503</td><td>Transaction declined because the amount exceeded the user’s monthly limit.</td></tr><tr><td>504</td><td>Transaction declined due to outstanding unpaid balances.</td></tr><tr><td>511</td><td>This error occurs when the customer already exists on the payment channel's side.</td></tr><tr><td>512</td><td>This error occurs when the customer already exists on the payment channel's side.</td></tr><tr><td>513</td><td>This error occurs when the merchant user is already existing on the payment channel's side.</td></tr><tr><td>551</td><td>Occurs when there is a duplicated refund request. This means that we already made the refund request for the transaction.</td></tr><tr><td>552</td><td>Occurs when the refund time has elapsed.</td></tr><tr><td>553</td><td>Occurs when the refund process fails.</td></tr><tr><td>554</td><td>This occurs when there is an error while the user is trying to make the payment. The funds are refunded to the user. No action is needed.</td></tr><tr><td>555</td><td>Refund request is in progress.</td></tr><tr><td>556</td><td>No matching refund record found for the request.</td></tr><tr><td>601</td><td>The voucher code that the customer entered is incorrect.</td></tr><tr><td>602</td><td>The voucher PIN that the customer entered is incorrect.</td></tr><tr><td>603</td><td>The customer entered the correct card information but chose the wrong card type.</td></tr><tr><td>604</td><td>The customer entered incorrect card details or attempted to use a card that had already been redeemed.</td></tr><tr><td>605</td><td>The voucher code entered by the customer has been used.</td></tr><tr><td>606</td><td>The voucher code entered by the customer has a mismatched value.</td></tr><tr><td>607</td><td>The voucher code entered by the customer has expired.</td></tr><tr><td>700</td><td>Occurs when the transaction with card payment is rejected.</td></tr><tr><td>701</td><td>Occurs when the transaction with card payment status is pending.</td></tr><tr><td>702</td><td>Occurs when the customer cancels the card payment from their side.</td></tr><tr><td>703</td><td>The customer entered incorrect card details or attempted to use a card that had already been exceeded.</td></tr><tr><td>704</td><td>This error occurs when a card has failed a risk assessment on Stripe and is denied by the bank. Please contact our technical team for support.</td></tr><tr><td>705</td><td>This error occurs when the card is expired.</td></tr><tr><td>706</td><td>This error occurs when the customer doesn't have a sufficient balance/limit on their card.</td></tr><tr><td>707</td><td>The issuer bank returns an error for the card payment.</td></tr><tr><td>708</td><td>Occurs when the customer inputs invalid card data.</td></tr><tr><td>709</td><td>Occurs when the transaction type of the card payment is not supported.</td></tr><tr><td>710</td><td>Occurs when the transaction using the card is blocked.</td></tr><tr><td>711</td><td>Occurs when the card authorization is failed.</td></tr><tr><td>712</td><td>Occurs when customers input the wrong CVV/security code number.</td></tr><tr><td>713</td><td>There's a duplicate transaction for the card payment.</td></tr><tr><td>714</td><td>Occurs when the card payment's address verification is failed.</td></tr><tr><td>715</td><td>Occurs when the card payment's transaction cannot be processed.</td></tr><tr><td>717</td><td>Occurs when customers input an invalid card's expiry date.</td></tr><tr><td>718</td><td>Occurs when customers input an invalid card password.</td></tr><tr><td>719</td><td>Occurs when customers input an invalid card's expiry date.</td></tr><tr><td>720</td><td>Occurs when the merchant uses an invalid payment method.</td></tr><tr><td>721</td><td>Occurs when customers input an invalid card's PIN.</td></tr><tr><td>722</td><td>Occurs when the customer's card has exceeded the limit.</td></tr><tr><td>723</td><td>Occurs when the card transaction is not allowed.</td></tr><tr><td>724</td><td>Occurs when the credit card's 3DS is not completed.</td></tr><tr><td>725</td><td>Occurs when the card exceeded its daily attempt limit.</td></tr><tr><td>726</td><td>Occurs when the IP address from the credit card exceeded its daily attempt limit.</td></tr><tr><td>729</td><td>Occurs when the amount is invalid.</td></tr><tr><td>731</td><td>Occurs when entered an invalid card number or an invalid  account number.</td></tr><tr><td>733</td><td>The issuer bank returns an error for the card payment.</td></tr><tr><td>736</td><td>Occurs when the transaction is invalid</td></tr><tr><td>739</td><td>Occurs when the payment has failed a risk assessment. Please contact our technical team for support.t.</td></tr><tr><td>741</td><td>Occurs when the card it's a lost card.</td></tr><tr><td>742</td><td>Occurs when the card is invalid.</td></tr><tr><td>743</td><td>Occurs when customers entered an invalid PIN.</td></tr><tr><td>744</td><td>Occurs when it exceeds the withdrawal amount limit.</td></tr><tr><td>745</td><td>Occurs when the transaction times out.</td></tr><tr><td>746</td><td>Occurs when the card is unsuable.</td></tr><tr><td>747</td><td>Occurs when the transaction is pending.</td></tr><tr><td>748</td><td>Occurs when customers entered an incorrect PIN.</td></tr><tr><td>750</td><td>Occurs when the payment has failed a risk assessment. Please contact our technical team for support.</td></tr><tr><td>751</td><td>Occurs when there has been a system error related to fraud.</td></tr><tr><td>752</td><td>Occurs when the transaction amount is greater thena preauthorised.</td></tr><tr><td>809</td><td>Occurs when the SKU is invalid,</td></tr><tr><td>901</td><td>Occurs when there has been an SMS delivery error.</td></tr><tr><td>902</td><td>Occurs when a customer with an MSISDN from an operator with whom Coda is not connected initiates a purchase.</td></tr><tr><td>903</td><td>Occurs when there has been an SMS delivery error.</td></tr><tr><td>904</td><td>Occurs when Coda cannot connect to a particular telco's system.</td></tr><tr><td>905</td><td>Occurs when Coda receives a response timeout from the particular telco's system.</td></tr><tr><td>906</td><td>The mobile operator with whom Coda filed a charge request was unable to deliver the SMS to the customer.</td></tr><tr><td>907</td><td>The MSISDN entered by the customer does not exist.</td></tr><tr><td>951</td><td>Occurs when Coda receives an MT access not available from the particular telco's system.</td></tr><tr><td>952</td><td>Occurs when Coda receives a notification that the MT access is for the subscription only.</td></tr><tr><td>953</td><td>Occurs when Coda received error subscriptions ineligible for MT from a particular telco's system.</td></tr><tr><td>970</td><td>This means the tokenized charge has been prenotified.</td></tr><tr><td>980</td><td>Occurs when the tokenized charge user has been authenticated.</td></tr><tr><td>999</td><td>This means the tokenized charge is under free trial.</td></tr><tr><td>1001</td><td>Occurs when the provided date of birth is invalid.</td></tr><tr><td>1002</td><td>Occurs when the account or code is expired.</td></tr><tr><td>1003</td><td>Occurs when the account is inactive.</td></tr><tr><td>1004</td><td>Occurs when the account is stolen or canceled.</td></tr><tr><td>1100</td><td>Occurs when the SKU ID is duplicate.</td></tr><tr><td>1200</td><td>Occurs when it is declined by the circuit breaker.</td></tr><tr><td>1300</td><td>Occurs when the payment channel configuration is empty in the error mapping.</td></tr><tr><td>1301</td><td>Payment channel closed/maintenance</td></tr></tbody></table>

{% hint style="info" %}
If you have more questions about the error codes, feel free to contact us for more detailed information through <technical@codapayments.com>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coda.co/codapay/error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.