A delayed payment is normal for a few business days after the close. A missed payment is different: the platform shows it as paid and your bank has no record. Knowing which one you face decides what you do next.
Start with the payments page. The status there tells you whether the problem is on the platform side or at your bank.
A delay still shows a processing status and a date. The money is in transit and will land.
A failure shows a cleared status with no matching deposit. That points to a wrong account number or a rejected transfer.
A hold shows the balance still pending with a note attached. Nothing left the platform, so the fix is on your side.
Check the status before you check the bank. The page tells you whose problem it is.
Give a normal delay its full window before you act. Weekend banking adds days that have nothing to do with your account.
Confirm your payout details are still correct. A method you updated mid cycle can send money to an old destination.
Contact support with the transfer date, amount, and status in your message. Vague tickets take longer to resolve than specific ones.
If support confirms the payment left, ask your bank to trace it with the reference number. Banks can find transfers that apps cannot.
Confirm a new payment method with a small payout before you route everything through it. One test beats an anxious month.
Keep your profile and bank details current so a routine change does not land in the middle of a payout cycle.
That minimum balance before money moves out is called the payment threshold, and it shapes when every creator gets paid on GoScript in practice.
Payout timing on GoScript follows a monthly close, and knowing the exact dates helps you plan bills and savings before the money lands on time.
Setting up a payment method on GoScript takes a few minutes, but the details you enter decide how fast future payouts arrive once they clear.
Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.
Analyze a Channel